Actually pass through Sentry env vars to production deployment

[vcarl]

I had observed that no production events were being ingested into Sentry, which is definitely not correct. This should resolve it, and will log configuration details so we can inspect what's happening

[what-the-diff]

PR Summary

• GitHub Workflow Configuration
  An update to add new confidential variables SENTRY_INGEST and SENTRY_RELEASES to node.js operations in our automated system.
• Server Environment Enhancement
  The new confidential variables mentioned above are now retrievable through two newly introduced constants (sentryIngest and sentryReleases) in the server setup file.
• Error Tracking System Configuration
  The setup process for our error tracking system (Sentry) has been updated. It now uses the sentryIngest constant for key tasks, and all of its options are neatly packaged in a dedicated object. There's also a new log statement added to confirm the system's configuration.
• Secured Cookie Organization
  The system determining the security level of cookies has been improved by replacing direct reference to the environment variable with the use of a method that checks whether it's a production environment or not. This should offer enhanced clarity and maintain consistency.