Add enum for environment names

[whabanks]

Summary | Résumé

We had an incident where the RTE feature was to only be enabled if the current environment != production. However the comparison string used PROD instead of production.

This PR will:

• Add a place for enums to live, in app/enums.py
• Add a new enum called NotifyEnv
• Registers the enum in jinja_env.globals for quick access in jinja templates

Jinja Usage:

{% if config["NOTIFY_ENVIRONMENT"] != NotifyEnv.PRODUCTION.value %}
...

.py files

from app import NotifyEnv

if current_app.config["NOTIFY_ENVIRONMENT"] != NotifyEnv.PRODUCTION.value:
...

Test instructions | Instructions pour tester la modification

CI is passing

• If you really wanna test, add checks from above to a jinja template and / or endpoint and set breakpoints.

[github-actions]

🧪 Review environment

https://njeevqalls544so3sdvdr7k5fu0xnuff.lambda-url.ca-central-1.on.aws/

[andrewleith]

Should we use these in config.py as well?

[whabanks]

Should we use these in config.py as well?

That's a good idea, helps with visibility too. I've added them to config.py and refactored existing checks to use the Enum.