refactor(jetsocat): implement better coloring control for logging

[RRRadicalEdward]

This PR improves coloring control as requested in https://github.com/Devolutions/IronVNC/pull/988#pullrequestreview-3303353388.

[github-actions]

Let maintainers know that an action is required on their side

• Add the label release-required Please cut a new release (Devolutions Gateway, Devolutions Agent, Jetsocat, PowerShell module) when you request a maintainer to cut a new release (Devolutions Gateway, Devolutions Agent, Jetsocat, PowerShell module)

• Add the label release-blocker Follow-up is required before cutting a new release if a follow-up is required before cutting a new release

• Add the label publish-required Please publish libraries (`Devolutions.Gateway.Utils`, OpenAPI clients, etc) when you request a maintainer to publish libraries (Devolutions.Gateway.Utils, OpenAPI clients, etc.)

• Add the label publish-blocker Follow-up is required before publishing libraries if a follow-up is required before publishing libraries

[RRRadicalEdward]

In tests, assert_cmd is used to run jetsocat in a child process, where stderr is piped. This means that we always have is_terminal = false. That's why, for example, log_term_coloring with the default case will return false.

[CBenoit]

I’ll investigate if we can still check the TTY case properly.