Run test publish workflow on push to release/ branches

[danielhollas]

I noticed when releasing version 2.2.0 that the test publish workflow was not triggered on the PR in #593. This was my mistake: At some point I changed the triggering event from push to pull_request. However, the branches filter that we use so that the test-publish is only run on release branches, has a different semantic meaning for pull_request event --- it specifies the target branch, not the branch that is being merged.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.21%. Comparing base (1bba240) to head (3e60c9b).
Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #594   +/-   ##
=======================================
  Coverage   96.21%   96.21%           
=======================================
  Files          11       11           
  Lines        1188     1188           
=======================================
  Hits         1143     1143           
  Misses         45       45           

Flag	Coverage Δ
python-3.10	96.21% <ø> (ø)
python-3.9	96.21% <ø> (ø)

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]

jumanjihouse/pre-commit-hook-yamlfmt#23

[danielhollas]

@yakutovicha can you take a look?

Note that the publish workflow as specified here was there basically as is before I made any changes, the idea that you can inspect a release by first releasing on TestPyPI, where you can then inspect the package. But practically this couldn't really be used with bumpver, since you'd always push to master. (not saying which is better, just providing context).

[danielhollas]

Going to merge this, since we need to release a patch version.