Maintenance: change workflow inputs to always use `env`

[dreamorosi]

Summary

SonarCloud has surfaced a number of areas for improvement in our CI workflows where the workflow inputs are used directly inline in some comments rather than creating intermediate environment variables.

We should fix this and use env variables wherever possible.

Why is this needed?

So that we can improve the input processing of our CI workflows.

Which area does this relate to?

Other

Solution

No response

Acknowledgment

• This request meets Powertools for AWS Lambda (TypeScript) Tenets
• Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET

Future readers

Please react with 👍 and your use case to help us understand customer demand.

[powertools-for-aws-oss-automation]

Warning

This issue is now closed. Please be mindful that future comments are hard for our team to see.
If you need more assistance, please either reopen the issue, or open a new issue referencing this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

[github-actions]

This is now released under v2.27.0 version!