Overhaul multiplayer text system

[AbnerSquared]

The multiplayer framework has a weak text system, often relying a lot on the Draw() method. This overhaul should make it much easier to handle text formatting.

Rough Steps:

• Replace Component to TextContainer
• Create an abstract class BaseTextContainer
• TextContainer values should utilize a set string format, with variables that can be specified in it
• TextContainer values should mimic the Buffer system from the original Component classes
• TextContainer values should have more methods related to formatting, such as markdown implementation, padding and text alignment, and other scenarios
• TextListContainer should also be implemented as a way to easily introduce lists, similar to ComponentGroup
• TextListContainer should have base text formatting, individual element formatting, and a separator
• TextContainer values should now be able to specify a character limit to block off extremely long lines of text
• TextContainer values should include automated pagination support, which can be peeked at by jumping to an index
• To prevent out of range errors, TextContainer pagination methods should revolve around TryMoveNext, TryMovePrevious, First, Last, which will attempt to jump to the specified pages
• All missing text values in a TextContainer should instead be noted by a INVALID_VALUE or a VALUE_NOT_SPECIFIED, as opposed to errors
• Errors can easily be toggled depending on how severe text issues are
• The BaseTextContainer class should be easily accessible and customizable
• The BaseTextContainer class should expose core methods and properties that inheriting classes can manipulate or modify for their own purpose