[Cloud Security] Create Serverless QA Environment

[Omolola-Akinleye]

Summary of your changes

This PR creates a Serverless QA Environment. In this PR we updated Mask Sensitive Data to update the TF_VAR_ec_api_key with the secrets QA API KEY when input.ec-url is https://console.qa.cld.elstc.co.

Also, we added options

Screenshot/Data

Related Issues

elastic/kibana#176748

[github-actions]

📊 Allure Report - 💚 No failures were reported.

Result	Count
🟥 Failed	0
🟩 Passed	359
⬜ Skipped	33

[gurevichdmitry]

@Omolola-Akinleye, The last workflow's successful run didn't involve destroying the environment. Can you please ensure that the destruction process is also functioning correctly?

[Omolola-Akinleye]

@Omolola-Akinleye, The last workflow's successful run didn't involve destroying the environment. Can you please ensure that the destruction process is also functioning correctly?

@gurevichdmitry I created another workflow and also deleted the workflow.

[gurevichdmitry]

@Omolola-Akinleye I'm unsure if this is the appropriate location to request the TF_VAR_qa_ec_api_key. Since I intend to delete a production environment, the TF_VAR_qa_ec_api_key isn't necessary. If I define it here, both keys would be required.

[gurevichdmitry]

@Omolola-Akinleye I've updated the branch and it appears that the CI is failing due to linting issues. Could you please fix them?

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b qa-dev-env upstream/qa-dev-env
git merge upstream/main
git push upstream qa-dev-env

[Omolola-Akinleye]

Closing PR as result of QA environment being created