Workflow fixes

[slamb2k]

Motivation and Context

• The deployment workflows have a id-token permission at job level which overwrites the top-level. Not a problem if the repo is public but breaks it if you change to private as checkout can't find the repo.
• The "stable" environment deployment needs to depend on the earlier builds for artifact names. Without them it, the "stable" deployment fails

Description

• Moving id-token up ensures both permissions apply.
• Adding builds as "needs" for "stable" ensures dependencies are available for deployment

Contribution Checklist

• The code builds clean without any errors or warnings
• The PR follows the Contribution Guidelines and the pre-submission formatting script raises no violations
• All unit tests pass, and I have added new tests where possible
• I didn't break anyone 😄

[crickman]

Gil, can you verify how this intersects with your efforts?

[slamb2k]

My apologies, I just realised Gil has already submitted a PR that fixes the "stable" part of the release pipeline. I can close it and resubmit another one containing just the permissions change if you like.

[crickman]

Up to you on how you'd like to manage the change. If Gil's PR completes, just merging to current might be an option also...your call.

[glahaye]

@slamb2k I just took your PR as it is a superset of mine.

Thanks for your changes!