ref(publish): Add sentry-javascript/master branch to target-repo-branch step

[Lms24]

This PR adds the master branch to the allowed branches we can take the craft config file from in sentry-javascript.
IMHO we should allow taking the config from master as well as from v7 (as done in #3467):

• Our repo's default branch is develop while we release from master (more information on our gitflow approach). So there is a chance that the craft config on develop is not aligned with the config on master, for instance in the case where the config is changed while a release is still in progress.
• I'd like to avoid using two different strategies of obtaining the craft config (i.e. once via the new opt in mechanism, once in the default way), which 1. increases consistency and 2. makes it easier for everyone on the team and surrounding teams to create releases, regardless of v7 or current version (v8)
• Branch protection rules for master and develop are aligned, so this requirement should be fulfilled.

[asottile-sentry]