Modifying the Allowed Users settings to use env.ALLOWED_USERS

[emvaldes]

This PR is aimed to fix the existing hardcoded configuration of allowed users for deployment's rollback to be driven by an environment variable which will in time allow for this variable to be modified without affecting or triggering any build process and enhance compliance with active-users.

Note: This is not an exploitable issue or any security concerns but rather an administrative functionality that must be addressed to maintain accuracy on which resources are actively involved in the process considering the dynamics of resources management in this project.

Configuration Steps:

• Created an repository variable ALLOWED_USERS with the existing users to avoid any process disruption.

Changes

• Requesting feedback from all teams on who should be added to this list (it must be updated A.S.A.P.)
  Current users: lucasdze,jeremy-page,JosiahSiegel,snesm,supriyaaddagada

Checklist

Testing

• No testing is involved in this PR other than notifying all involved parties.

Process

• Creating the repository variable ALLOWED_USERS
• Updating the repository variable with the correct and authorized users
• Updated the performed changes to the workflow with relevant notes
• Development and DevSecOps team has been notified

Linked Issues

• This is not a fix to any existing issue.

To Be Done

• A GitHub issues is already created: Update the deployment_rollback ALLOWED_USERS list to reflect current resources

Security-related subjects:

• This PR does not introduce any new dependencies that need vetting and it does not log any sensitive data but it does provide certain level of masking to those users allowed to rollback deployments.

[devopsmatt]

LGTM