chore: Refactor logging & avoid logger errors caused by SDK debug printing

[limbonaut]

Refactors engine logging in preparation for structured logs (#409).

This PR:

• Relocates SentryLogger to the logging namespace and renames it to SentryGodotLogger.
  • This is internally used engine logger -- added detailed description in comments.
  • The renaming is needed as we're introducing structured logs and need to expose SentrySDK.logger interface in the API, which will take over the SentryLogger class name.
• Moves print.h to the logging namespace, as it belongs there.
• Improvement: Implements detection to identify when we're inside message logging, preventing print operations through the Godot logger to avoid runtime errors.

[jpnurmi]

Did you consider some completely different name? Maybe something like "console" could work? Feel free to ignore if it sounds silly - just thinking out loud... :)

[limbonaut]

Did you consider some completely different name? Maybe something like "console" could work?

Yeah, I know. It's called Logging in Godot and console doesn't really fit either. In the end, I decide to call the Godot subsystem "logging" and the sentry part "structured logs". But it's the class names right? The base class for Godot's is Logger and it's hard to figure something that would fit here and is not Logger. My other candidates are SentryEngineLogger and SomethingLoggerIntegration.

UPDATE:
We also have logger_* options that affect engine logger, so keeping "Logger" in class name is probably a good idea.