Consider enabling staleness bot for etcd/etcd

[jberkus]

In etcd-io/etcd, we have 202 open issues going back to 2016 (which I think is the year after we launched etcd). There is no way we're actually going to review all these issues; in the triage meetings we never go back past the last month.

As such, I propose that we enable the staleness functionality of k8s-ci-bot. This would result in issues auto-closing if they've had no activity within a defined period, probably 6 months. The reminders it sends are also a good prompt for people to update their issues.

[ahrtr]

I believe the auto-close has already been enabled. Not sure why the older issues are not closed.

[jberkus]

Either it's not running, or it's configured in a way that it can never actually close anything.

[ivanvc]

The configuration for the stale bot is here: https://github.com/etcd-io/etcd/blob/main/.github/workflows/stale.yaml. If it's not closing issues, it should be due to the labels they have.