[MRRTF-202] MUON: improve handling of QC for MCH-MID matching

[aphecetche]

The MFT-MCH and MFT-MCH-MID will be handled the same way later on.

@aferrero2707 this is the version (MCH+MID) we tested a few weeks ago.

I assume that :

• this can not be (undrafted and) merged before the other changes (QC and ControlWorkflows) are done
• we will first put this in production with just MCH+MID and only later on uncomment MCH+MFT+MID ?

Let me know,

[aferrero2707]

@aphecetche I would propose to proceed as follows:

1. already include in this PR all the possible matching combinations
2. wait until the new QC is deployed to P2
3. update consul://o2/components/qc/ANY/any/muon-qcmn-epn-mch-mid and consul://o2/components/qc/ANY/any/mch-qcmn-epn-full-track-matching with the configuration parameters expected by the new code (this way we can use the new QC with the current version of ControlWorkflows and O2DPG)
4. introduce the additional JSON files in consul, namely consul://o2/components/qc/ANY/any/muon-qcmn-epn-mft-mch and consul://o2/components/qc/ANY/any/muon-qcmn-epn-mft-mch-mid
5. run a test with ControlWorkflows and O2DPG from the development repositories, checking all possible matching combinations
6. if all is ok, un-draft the ControlWorkflows and O2DPG PRs
7. once deployed to P2, they will automatically pick up the new JSON files that are already tested and validated in step 5

What do you think?

[benedikt-voelkel]

Closing, no movements since more than a year now.
Reopen if needed.