392 force uppercase module subscriptions

[mudinthewater]

Fixes: #392

1. Corrects order of operations in assigning a module to an EVR stream request.

Before:
domainObject.telemetry.definition.module first
domainObject.telemetry.evr_name.split("_")[0] if evr_name existed
domainObject.telemetry.module third

This caused it to break if modules had an underscore in them, and would also cause it to default to the legacy EVR name method before using the module definition from the dictionary.

Now:
domainObject.telemetry.definition.module first
domainObject.telemetry.module second
domainObject.telemetry.evr_name.split("_")[0] as a last ditch resort.

This should work for cases where the module has underscores now, as the module provided by the EVR dictionary will be used in all cases before trying to assume a module from the evr name.

2. Makes module stream requests all caps and all internally consistent.
   There were instances where an EVR return would have an all caps module name, but OMM was forcing all lowercase module names in the evr stream. This caused a disconnect with the MCWS return so no EVRs would appear in module streams.

MCWS is case-agnostic for EVR streams, so best method here is to make stream requests internally consistent - other filters use all caps already (well, they use the dictionary default which is all caps), so we should also use it for both the request and the key.

[mudinthewater]

NOTE:

1. MCWS appears to be case-agnostic for all filters. We should verify this, in particular check that these are case agnostic:

   openmct-mcws/src/realtime/MCWSMessageStreamProvider.js

   Line 19 in 17ef68f

   if (messageType === 'CommandMessages') {

2. DO not merge this until: every key has been uppercased. The above code is either:

a. Assuming the key is uppercase (bad and what originally got us in this mess)
b. Forcing an uppercase filter.