Add bumpver pre-commit

[danielhollas]

This is the last piece in the release workflow.

The newly added bumpver_pre_commit.sh script is configured to run automatically by bumpver
before it creates the release commit.
We check for common mistakes, such as making a release commit
in a wrong branch, or trying to push to a wrong remote.

For now, only two checks are implemented:

1. Check that the current branch name matches either release/* or support/*

2. Check that the remote origin is pointing to the origin repository,
   and not a fork. Note however that this assumes that origin is the default remote
   where new branches are pushed. If the user configured a different default remote,
   this check will not save them in the current implementation.

Future work:

• make sure the main branch is up-to-date with origin/main
• make sure the HEAD commit was branched off of main branch,
  although this rule should only apply to release/* branches, not support/* branches
• check what is the default push branch

It would be great if at least some of these checks were handled by bumpver itself:

Restricting releases from branch: mbarkhau/bumpver#198
Restricting releases to specified remote: mbarkhau/bumpver#234

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 75.79%. Comparing base (f63da7d) to head (8022f49).
Report is 73 commits behind head on main.

❗ Current head 8022f49 differs from pull request most recent head 00873c0. Consider uploading reports for the commit 00873c0 to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #688      +/-   ##
==========================================
- Coverage   80.73%   75.79%   -4.95%     
==========================================
  Files          49       59      +10     
  Lines        3415     4767    +1352     
==========================================
+ Hits         2757     3613     +856     
- Misses        658     1154     +496     

Flag	Coverage Δ
python-3.10	75.79% <ø> (-4.95%)	⬇️
python-3.8	?
python-3.9	?

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[danielhollas]

@unkcpz @superstar54 friendly ping (I know you're busy) to review this so that we can start testing this for the releases. Thanks!

[superstar54]

Hi @danielhollas I looked it this morning. I am not very familiar with this. But LGTM!

[danielhollas]

@superstar54 thanks for taking a look. Feel free to merge so you can test it while doing releases.
I think you will want to recreate the rc2 release PR #701 anyway to pick up the most recent commits on main, so this might be a good opportunity for a test.