What problem does this address?

Currently the plugin's zip file is generated upon each commit and stored in the associated action run for each commit on trunk.

For example the artifact for 1df91fb can be found attached to action run 10856201819.

As the release/* and wp/* branches are also production branches, generating the artifact for these commit branches would be helpful for contributors wishing to test the branches

What is your proposed solution?

Add the WordPress and Release branches to the push section of the build-plugin-zip workflow file.

This workflow also includes the npm-publish job so any changes would need to make that portion of the workflow only runs when appropriate. I'm happy to work on the PR for this but it would be good to get some advice to make sure I don't end up triggering a package publish on each push to these branches.

cc @gziolo