Separate component styling into a ComponentStyle class

[2008Choco]

With the introduction of scoreboard number formats, specifically the minecraft:styled format, Mojang clearly makes a point that component styling can be independent from the contents of a text component. This PR separates all text styling fields into its own ComponentStyle class with its own builder and adds BaseComponent#applyStyle(ComponentStyle) and ComponentBuilder#apply(ComponentStyle) methods to apply these styles.

ComponentStyle instances are mutable but can be cloned or edited into a new instance with ComponentStyle.builder(ComponentStyle).

[md-5]

Needs a way to parse a style.

Also throwing out the idea that BaseComponent could extent ComponentStyle instead of having it as a field, but I don't have a preference for either at the moment.

[2008Choco]

Needs a way to parse a style.

Yeah, I'll add a way to parse now

BaseComponent could extent ComponentStyle instead of having it as a field

I disagree with this. I think composition vs inheritance decision making applies here. Component doesn't fit the bill for "is a style" but it does fit "has a style", so a field here makes the most sense imo despite the unfortunate need for repetition.

[md-5]

I think we still need ComponentSerializer#parseStyle or something for use with scoreboards (and wherever else there is a style)

[2008Choco]

I think we still need ComponentSerializer#parseStyle or something for use with scoreboards (and wherever else there is a style)

Oh, yeah, for server internals. Will add that. My bad.

[mrjasonn]

It seems like this PR is done, probably can be merged?

[md-5]

Thanks