Fix formatting of remote debug logs

[HugoW5]

Description:

• Added isTerminalLogger() to httpLogFilter to detect if the underlying logger writes to a terminal
• Exposed IsTerminal() on the base logger to allow querying terminal output capability.

Benefits

• Prevents ANSI color codes and non-ASCII characters from appearing in JSON logs.
• Keeps terminal debug logs readable with colors.
• Ensures downstream log processors can reliably parse JSON logs.

Related Issue

Fixes #2281

Additional Information:

• Terminal output (colored debug logs):

• JSON file output (plain, color-free logs):

Checklist:

• I have formatted my code using goimport and golangci-lint.
• All new code is covered by unit tests.
• This PR does not decrease the overall code coverage.
• I have reviewed the code comments and documentation for clarity.

[Umang01-hash]

Hey @HugoW5 Thanks for the PR — this is a useful quick fix.
But we should avoid using IsTerminal() or a type-assertion in the filter; since it duplicates terminal vs JSON formatting and can leak ANSI into JSON logs.

A cleaner approach could be we can add a small typed message in remotelogger (for example httpDebugMsg) that:

• Implements logging.PrettyPrint to render ANSI-colored output for terminals.
• Implements json.Marshaler / MarshalJSON to return an ANSI-free string for JSON/file logs.
• Replace the Debugf(...) branches with a single f.Logger.Debug(msg) call, passing the httpDebugMsg instance.

[HugoW5]

@Umang01-hash
Thanks for the heads up, i can propose a better solution later this week!