C2MS12 — namespace support should be reflected in at least the telemetry and command related C2MS messages

Many t&c systems support some form of namespaces in their database definitions. For example a "parameter" might be associated with a certain namespace ("/myagency/mymission/mysystem/mysubsystem/batv1") or a command as well. XTCE supports a kind of namespace through the spacesystem tree. GSFC's ITOS supports namespaces in the database. (the other one, ASIST does not). And so forth.

Add optional namespace field and optional ns format field with default

Ns is a string. Nsf is default "xtce" but also a string. Both optional. xtce means it's in xtce form /which/is/like/this.

The default can accommodate other implementation specific forms but the xtce must be supported.

The namespace should be associated with parameters, packets and commands.

The following C2MS messages are affected:

• Telemetry CCSDS Packet Message
• Command Request Message
• Command Response Message (maybe)
• Command Echo Message
• Replay Telemetry Data Messages
• Telemetry Processed Frame Message
• Telemetry TDM Frame Message
• Replay Telemetry Data Request Message
• Replay Telemetry Data Response Message
• Mnemonic Value Request Message
• Mnemonic Value Response
• Mnemonic Value Data Message
• Archive Mnemonic Value
• Archive Mnemonic Value Response Message
• Archive Mnemonic Value Data Message