Restrict Privacy Center debug logging to development-only

[NevilleS]

Closes #3637

Code Changes

• Wrap remaining console.log statements in Privacy Center code with a NODE_ENV == "development" guard

Steps to Confirm

• Run turbo dev and confirm the "Load Privacy Center environment...", "Loaded configuration file.." logs are still present locally
• Run nox -s "fides_env(test)" and confirm Privacy Center logs are quiet

Test Results: Development

Test Results: Production

Pre-Merge Checklist

• All CI Pipelines Succeeded
• Documentation:
  • documentation complete, PR opened in fidesdocs
  • documentation issue created in fidesdocs
• Issue Requirements are Met
• Relevant Follow-Up Issues Created
• Update CHANGELOG.md
• For API changes, the Postman collection has been updated

Description Of Changes

I personally added some troubleshooting logs to the Privacy Center backend for loading config files, but didn't really think them through - these fire on every request, so we really can't log anything for "normal" troubleshooting!

NextJS doesn't have thorough support for log levels like DEBUG/INFO/WARN/etc., so that kind of "normal" solution doesn't apply here, so I'm just disabling the logs based on the NODE_ENV instead.

[RobertKeyser]

Approved, but in the future it might be good to use either an enum or const for the env "development". That can be a future improvement though.

[cypress]

Passing run #2835 ↗︎

0	4	0	0	0
⚠️ You've recorded test results over your free plan limit. Upgrade your plan to view test results.

Details:

Merge f3eb293 into f20e299...
Project: fides	Commit: 5aa2e9fc8c ℹ️
Status: Passed	Duration: 00:50 💡
Started: Jun 21, 2023 3:02 PM	Ended: Jun 21, 2023 3:03 PM

_{This comment has been generated by cypress-bot as a result of this project's GitHub integration settings.}