TTYPE should track all listed options #202
Description
In short, this is probably a simple matter of having a List that we populate next to TerminalOptions.TerminalType which we add each unique string to. It should probably also have a reasonable but generous max to how many we populate (to avoid infinite memory growth attack), maybe 40 total items? 40 is also the max item string length (we should cap it to avoid growth as well), per:
(https://www.iana.org/assignments/terminal-type-names/terminal-type-names.xhtml)
Basically, it seems like a MUD should have an avenue to use reported TTYPE options to make decisions about what the client can receive and handle, even if it is no the "active" default option reported - which could be a matter of querying a TerminalOptions List to see if a given option is within.
Once this is done, we may want to create a new ticket to: Study what kinds of ttype entries are reported commonly by common clients, to see what other features we may want (e.g. perhaps systemizing determiniation color modes available in addition to giving the user a way to override the automatic detection)