[INFRA] Set up default rulesets for default and release branches

[asf-gitbox-commits]

This Pull Request enables the repository to conform with the "sane default security settings" of the Apache Software Foundation by configuring a default branch ruleset that protects the default branch and any release branches.

Note that ~DEFAULT_BRANCH is a GitHub symbolic link to the current default branch (HEAD) of the repository and does not need changing.
If the managing project does not wish to set up these defaults, please close this Pull Request. Alternatively, the project may merge this Pull Request to apply the changes immediately.

If no action is taken, this Pull Request will be automatically merged by the Apache Infrastructure team on 2026-06-14 (30 days from now).

For any further information, please reach us on Slack or at: users@infra.apache.org

[ctubbsii]

ZooKeeper currently uses release-0.0.0 for its tags, with some additional variations, which does not match these patterns.

I think now would be a good time to start using a better naming convention for tags, as in rel/zookeeper-0.0.0 to put all the releases in a namespace. Alternatively, it could be rel/0.0.0, but I think that's not a good option, because it's better to have the name of the release in the tag, because repositories can be cloned with other names. So, the tag name should be self-descriptive. Also, this leaves open the possibility of releasing other artifacts (like subprojects) using the same pattern, as in rel/zookeeper-examples-0.0.0 or rel/zookeeper-deployment-tools-0.0.0 (these are just examples), in the future.