[BLD] Do not trigger deploy on merge to release branches

[eculver]

Description of changes

This removes the release/** trigger from the trigger-deploy workflow so that deploys aren't created when hotfixes are merged to release branches. We want this to be a manual step for the time being to prevent unintentional deploys of the control plane when we are hotfixing the data plane.

• Improvements & Bug fixes
  • Prevents hotfix merges from triggering a deploy of code that is potentially behind what is deployed.
• New functionality
  • N/A - removes automation

Test plan

Manual testing -- we will have to manually deploy changes after merging hotfixes to release branches.

[github-actions]

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

• Can you think of any use case in which the code does not behave as intended? Have they been tested?
• Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
• If appropriate, are there adequate property based tests?
• If appropriate, are there adequate unit tests?
• Should any logging, debugging, tracing information be added or removed?
• Are error messages user-friendly?
• Have all documentation changes needed been made?
• Have all non-obvious changes been commented?

System Compatibility

• Are there any potential impacts on other parts of the system or backward compatibility?
• Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

• Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

[propel-code-bot]

This PR modifies GitHub workflows to prevent automatic deployment when changes are merged to release branches. This makes deployment a manual step to avoid unintentional deploys when hotfixing the data plane.

This summary was automatically generated by @propel-code-bot

[eculver]

for consistency...

[eculver]

There is some issue with the action runners that is completely unrelated to this change. It seems to be persistent. I'm going to merge this as it has nothing to do with this change -- this does not change the "PR Checks" workflow. I'm hoping that it's something about this PR that is broken and that the merge commit will yield a green.