Add releaseNewActionVersion environment gate to prevent accidental releases

[Link-]

Description

This pull request includes changes to the GitHub Actions workflow configuration to improve the publishing process. The most important changes are the addition of an environment for the publish job and some formatting adjustments.

Motivation and Context

We don't want accidental and non-gated releases of immutable action packages. releaseNewActionVersion is a gated environment and will require approval before release.

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation (add or update README or docs)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[joshmgross]

cc @Jcambass - I'm curious if we should standardize this process across the actions org