Refactor Better ChatPrint and fix size limit

[Derpius]

Changes

• Adds a new TASUtils.getChatPrintMessageSizeBits global to calculate the size of a chat print message before trying to send
• Refactors encodeMsg to have a clearer name and to not check the message size mid-send
• Updates Broadcast and ChatPrint functions to check the message size and error before starting the netmsg
• Replaces net.WriteColor with net.WriteUInt
  • WriteColor uses WriteUInt under the hood, but this way we ignore some useless checks and have confidence in parity between our writer and size calculator functions
• Reduces max message size to 4KB

Impact

• Properly prevents overflowing net messages
• Exposes the size calculation func which allows for upcoming plycore changes to throw E2 errors when the message is too large

Testing

TASUtils.Broadcast and Player:ChatPrint() are essentially the same code, so can fully test one and then smoke test the other

• Calling with no arguments prints an empty string to chat
• Calling with one or more strings prints those strings to chat
• Calling with colours and strings correctly colours the chat.AddText message
• Arguments that are neither colours nor strings are stringified
• Throws an error when the total message is larger than 4KB
• Passing more than 255 arguments truncates to 255

[yogwoggf]

LGTM 👍

Will do a QA soon

[yogwoggf]

QA Result: Failed ❌

• Calling with no arguments prints an empty string to chat ✅
• Calling with one or more strings prints those strings to chat ✅
• Calling with colours and strings correctly colours the chat.AddText message ✅
• Arguments that are neither colours nor strings are stringified✅
• Throws an error when the total message is larger than 4KB ✅
• Passing more than 255 arguments truncates to 255 ❌
  • Passing more than 255 args doesn't truncate, but instead drop the entire message completely, leaving a blank line in the chatbox.
  • 
  • For clarity, the 256 message didn't throw an error, it silently failed.

[yogwoggf]

Forgot to approve