Update deploy.yml triggers

[alexjhawk]

Update the triggers of the deploy.yml GitHub action to allow for manual running as well as proper auto-dispatch when any new release is published (stable or pre-release).

[alexjhawk]

@it-hms I am updating the S3 action -- it didn't trigger automatically today.

Updating the triggers of the deploy.yml action to allow for manual triggering (in future cases where the action may not automatically start as expected) and so it starts automatically when any release is published.

I don't know why released did not trigger because I would have expected it to have, but that trigger needs to be changed regardless.

• released does not include pre-release types (which I'm nearly sure you added support for in S3)
• Based on a note for the prereleased type, which I assume applies equally to released, the event is not triggered when a release is published from a draft.
  • https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#release

  • Note: The prereleased type will not trigger for pre-releases published from draft releases, but the published type will trigger. If you want a workflow to run when stable and pre-releases publish, subscribe to published instead of released and prereleased.

• Switching to the published trigger should properly start the action when any release is published (stable or beta/pre alike) and cover the scenario where a release is published from a draft.
  • It's difficult to debug GitHub action triggers such as this to know for sure, but the GitHub action we use for automatically releasing connector builds could make a draft and then release that, which would explain deploy.yml not starting in this case.