Improve Sentry configuration

[arkid15r]

Describe the solution you'd like
For both backend/frontend make sure we set environment and release values. While environment is pretty straightforward, the release can be tricky: for staging we can use git commit SHA (the short one), whereas production should use real release version. In both cases the release values can be populated via ci/cd .env files generation.

Additional context

• https://docs.sentry.io/platforms/python/configuration/releases/
• https://docs.sentry.io/platforms/javascript/configuration/releases/

[harsh3dev]

@arkid15r I have understood the issue but I am not able to figure out how I can get the value of the latest release for production.
Is there any version.txt for that?

[arkid15r]

For production we have this trigger, so later for frontend and backend we could use GitHub release tag.

I hope this helps