Version db management

[m-kuhn]

The available registries currently update the version db automatically whenever new commits land on the main branch. The downside of this is, that branch protection cannot be enabled, as otherwise the automation doesn't have the required permission. I don't think this is ideal

Ideas:

a. accept this
b. look into ways to bypass this (I could imagine with a PAT we could use at least some of the branch protection options)
c. write a bot that helps to update the version db inside a pull request
d. write a pre-commit hook which will automatically run the version db update on the developer machine on commit

[Thomas1664]

I'm in favour of option d because this is the most convenient option and has no risk for interference with actions by other people.
The issue with PR bots is that you have to pull before you can make further changes.

[m-kuhn]

@autoantwort do you have an opinion on that? You were motivated for an automation on the main branch in the past https://github.com/orgs/open-vcpkg/discussions/1#discussioncomment-8332141)

[m-kuhn]

FYI: I drafted a pre-commit hook to format manifests (see open-vcpkg/python-registry#17)