WIP: Use first event type in EventStreamInfo to set Mc channel number

Should there be more than one type of event in the output stream this is reflected as a list of EventTypes in the EventStreamInfo. This far the FileMetaData would only accept a single event type in for setting the MC channel ID. This change should ensure that there is a reasonable number in the FileMetaData, even in the case of ambiguity.

It should be possible to put this into all 21.X releases.

changed the description

mentioned in merge request !37410 (merged)

added 21.0 label

added alsoTargeting:21.1 alsoTargeting:21.2 alsoTargeting:21.3 alsoTargeting:21.6 alsoTargeting:21.9 labels

Tag: @zmarshal @akraszna @gemmeren @amete @tsulaia

There should be no conflicts, but this is in purpose associated with: !37410 (merged)

After speaking with @amete we agreed that this is not necessary. No derivation tasks should take input from AODs with multiple types of events to produce DAODs. Closing.

closed