Restore deprecated legacy color codes in console with config

[jamespglines]

I know the reason for remove this. It cause issue and confuse for some messages in console and legacy color is deprecated and legacy. Many plugin use this. It is hard to remove at random time with no warning (ik color are deprecated. there is no direct warning about log).

In kyori I hear about "ansi component serializer". I think maybe this should wait until ansi serializer exists.. By restore with config this provide the better deprecation period and notice. small brown out.

I default to true. I do this because if it is not, many plugin will auto set to true. This is not good idea. I put deprecated in the config name to be clear for users who read.

Thank you for consideration. This is my first PR. I hope I read the contrib guidelines correctly 😅

This provide temp fix for #7590, #7560, #7662. To kangaro: this is not made because of you. do not put me on memecademy. let ur ego suffer.

[zml2008]

There's already a way to log colored text to console -- with the ConsoleCommandSender.

An ANSI serializer is purely an implementation detail -- the real solution for full-featured Component logging is via a Component-supporting SLF4J wrapper, see KyoriPowered/adventure#731. This is a relatively simple feature to implement, so I see no reason to implement workarounds rather than the correct solution

[jamespglines]

Yes. you can do this. but change is made so quickly and there is NOT good alternative of logging component to console yet. this is what i mean by ansi serializer. sorry for bad sentences.

This even break paper dev own plugin EssentialsX!

[jamespglines]

Why is this closed? If this workaround is not to be considered please say. this is ok. I want to know if my code is bad or if workaround never will exist.

[jpenilla]

This workaround will not be considered, however if it was to be considered, then the issue would be with the poor implementation.

[electronicboy]

This workaround mangles much more than it looks like it should need to and just looks to create its own set of issues in the process

I'm somewhat iffy around adding extra legacy handling for something we've advised against for years, I'm not hard against this, but, most instances of colour on the console are either generally abuse of the logger which can create issues, or stuff like chat, in which people should generally be using the console sender as vanilla does rather than using the logger

[jamespglines]

This is understood. Thank you for your time.

[zml2008]

Here's a more long-term solution to this issue: KyoriPowered/adventure#757