[Project] Improve logging

[kmcginnes]

Support around Graph Explorer is a bit tough because there is not much logging within the Graph Explorer logic.

There are things we must consider when scoping out this project.

• Do not accidentally expose user data
• Logging on the client must be sent to the server to be persisted
  • Alternatively, logging on the client can be stored in local storage and a "submit logs" type UI can be added to send logs to support
• Will likely need controls to allow toggling different levels of logging
• Will need to consider both AWS customers and open source individual users

Related Issues

• Original source [Feature Request] Improved logging for troubleshooting (2024 Roadmap item) #299

Tasks

• [Spike] Investigate options
• [Task] Add abstraction around console.[log|warn|error] in the client
• [Task] Add CloudWatch logging for server logs in Neptune Notebook #509
• [Task] Update SageMaker example and docs #510
• [Task] Add more logging in SageMaker lifecycle script #512
• [Task] Add error boundary to React #546
• [Task] Add settings page to app #513
• [Task] Add configuration in settings page to disable database query logging #540
• [Task] Add logging for Express errors #511
• [Task] Add database query logging from client #514
• [Task] Add request level logging in proxy server #515
• [Task] Add more granular error handling in client #516
• [Task] Add more verbose logging around database operations #518
• [Task] Validate environment value configuration #556