What would you like to be added?

Currently a number of files have OWNERS mapped to sig-api-machinery but they should be mapped to new sig-etcd. Currently this is impacting PR review and triage as etcd related PRs get triaged to api-machinery incorrectly. Ex:

• Build etcd image of v3.5.16 #127283
• Update etcd from v3.5.15 to v3.5.16 #127285

This issue tracks updating the currently incorrect OWNERS files and removing sig-api-machinery and adding sig-etcd.

The solution here would likely be:

• replacing sig/api-machinery w/ sig/etcd for directories that should be owned by sig/etcd (already done IIUC in Add sig/etcd labels for related directories #125679)
• removing sig/api-machinery from anything that is currently jointly owned which should be fully owned by sig/etcd
• use filters: (see https://www.kubernetes.dev/docs/guide/owners/#owners-spec, in repo OWNERS example here: https://github.com/kubernetes/kubernetes/blob/master/pkg/apis/OWNERS#L6) to make specific etcd files (eg: /hack/libe/etcd.sh) to sig/etcd

Why is this needed?

This is needed as currently PR review and triage for etcd related issues are mapped to api-machinery incorrectly.