automation: sync OWNERS_ALIASES changes from kubevirt/kubevirt and others

[dhiller]

          > @dhiller will we setup a job to open update PRs when OWNERS_ALIASES changes in kubevirt/kubevirt?

Yeah, I think automation around this would make much sense - not yet sure what exactly we want to do around this. I'd say we store lists inside community repo and sync from there

Originally posted by @dhiller in kubevirt/user-guide#819 (comment)

[kubevirt-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[kubevirt-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

[dhiller]

/remove-lifecycle rotten
/lifecycle frozen