Improve Safe MiniMessage Parser Control

[APickledWalrus]

Problem

While we have defined a set of MiniMessage tags we believe are best to parse automatically, some users may want more control over what is automatically parsed.

Solution

I have added a configuration option for controlling which tags are parsed by default. These can be supplied as specific tag names or the internal group used in MiniMessage (specifically, the name of the tag resolver in the StandardTags class). I have also done some reorganizing of the component parser class.

Safe Tag Changes

The primary intention (even before MiniMessage integration) was to prevent security issues from normal users sending messages with click events (e.g. to run malicious commands). That is, a common use case is something like:

set the chat message to the colored message

Ideally, this should only process safe formatting and not potentially dangerous formatting like click events. I'm not sure this worked super well on current versions (e.g. 2.14.3), but going forward, we'll establish that only some Style-related tags (colors, decorations) will be processed by default. These are the default tags listed in the configuration file.

Testing Completed

I added a small unit test covering some parts of the component parser.

Supporting Information

n/a

---

Completes: none
Related: none
AI assistance: none

[UnderscoreTud]

Could benefit from having a create safe and unsafe methods :)

[APickledWalrus]

That's the internal one so I figured it'd be okay