chore(test-env): add new environment named test in the deployment pipeline

[jimmypalelil]

Description

Adding a new test environment to our deployment pipeline (github workflows) to enable better testing and validation of changes before they reach production.

Type of change

Please delete options that are not relevant.

• 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 not work as expected)
• This change requires a documentation update

How Has This Been Tested?

The following tests were performed to verify the new environment setup:

• Deployment pipeline execution with the new test environment
• Environment variable configuration and isolation testing

Checklist

• I have read the [CONTRIBUTING](https://www.notion.so/CONTRIBUTING.md) doc
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have already been accepted and merged

Further comments

This change introduces a dedicated test environment in our deployment pipeline to improve our testing capabilities. The new environment will sit between dev and prod environments, allowing for more thorough testing of features before they reach prod.

[marcellmueller]

Nice! Excited to have test up and running 🥇

[hamidhabib-buttons]

(nit): If lower(var.target_env) is not a key in local.env_map, it will result in an error. I am wondering if we should do a lookup() first with a default fallback

[jimmypalelil]

imo it shouldn't default to any env and instead error out if it can't find it in the lookup table (env_map)