add new wf

[gurevichdmitry]

Summary of your changes

This PR introduces a new scheduled workflow to automatically destroy expired environments. Additionally, the existing workflow has been updated to support this functionality. TheCreate Environment workflow now includes a new input parameter, expiration_days, which specifies the number of days until the environment expires. This date is calculated and stored in the env_config.json file.

The Destroy Expired Environments workflow comprises two jobs: one for identifying expired environments and another for executing the destroy process. Due to limitations in the GCP environment deletion script, the destroy process is currently set to run sequentially.

Screenshot/Data

Expiration Days

Logging environments

Destroy Expired Environment WF

Related Issues

Checklist

• [ ] I have added tests that prove my fix is effective or that my feature works
• [ ] I have added the necessary README/documentation (if appropriate)

[mergify[bot]]

This pull request does not have a backport label. Could you fix it @gurevichdmitry? 🙏 To fixup this pull request, you need to add the backport labels for the needed branches, such as:

• backport-v./d./d./d is the label to automatically backport to the 8./d branch. /d is the digit NOTE: backport-skip has been added to this pull request.

[github-actions[bot]]

:bar_chart: Allure Report - :green_heart: No failures were reported.

Result	Count
🟥 Failed	0
🟩 Passed	359
⬜ Skipped	33