TMC handles initialization scenarios of setting and verifying Dish ID - VCC map

This feature is cloned from SP-3469 to capture the work remianing at the end of PI 20. It should be continued in PI 21. The original description is retained for reference.

---------------------------------------------

DISH ID is inserted into data flowing from the DISH to MID.CBF. Each Mid.CBF VCC (Very Coarse Channelizer) handles digitized and packetized data from one dish, and is able to retrieve DISH ID from the received packets. In addition, to ensure that the connections are as expected, MID.CBF receives (or obtains) DISH to VCC Mapping Table via Monitor and Control path. When deployed, during initialization Mid.CBF loads the DISH to VCC Mapping Table via Telescope Model.
TMC provides interface to allow Operations to command Mid.CBF to load a particular version of the DISH to VCC Mapping Table, and to obtain the currently used version (TMC can obtain that from Mid.CBF via CSP.LMC).
Without DISH to VCC Mapping Table the MID telescope cannot be functional.

The design work to determine the format of the DISH to VCC Mappint Table, the location where the table is stored, the file names and the development work required to enable that the table can be accessed via the Telescope Model is responsibility ot the MID.CBF team. See https://jira.skatelescope.org/browse/SP-3611.

TMC only provides API to enable Operations to specify which version should be used, and to instuct the Telescope to load a different version when needed. TMC also ensures that CSP uses the correct version (as specified by Operations).

It has been agreed that TMC, in the same manner as Mid.CBF, will load the "DISH to VCC Mapping Table" during initialization, from a file via Telescope Model.
In addition, Mid.CBF should be able to receive an instruction (command) to load a particular version of the "DISH to VCC Mapping Table" (it could be the same of different version), and may allow user to specify DISH ID for an individual VCC (via an engineering interface).

Context:
The purpose of "DISH to VCC Mapping Table" is to tell Mid.CBF which dish is connected to which VCC (Very Coarse Channelizer). Mid.CBF will compare the DISH ID received from the dish with this table and raise ALARM if the actual setup is not as expected. This table will eventually have 197 entries and should be stored under version control, so that we keep historical data, and can, for each observation (SB/scan, establish what was the telescope setup.

Requirements:

• The "DISH to VCC Mapping Table" shall be under version control to allow operations to tell TMC and Mid.CBF which version to use.
• Operations/users shall be able to define different version of the table for different deployments (telescope, ITF, PSI, CI/CD pipelines).
• Operations shall be able to specify the version to be used for each deployment. The table shall be loaded during the telescope (TMC) initialization.
• TMC shall provide interface so that the Operations can instruct the Telescope (TMC and Mid.CBF) to load a different version of the "DISH to VCC mapping table" without a need to re-deploy software.
• It has been agreed that the Telescope Model is the best place to place this table. More precisely, the file containg the table will be stored on CAR, and the access will be via the Telescope Model.

Similar requirements apply for the dish coordinates. It is to expect that the "DISH to VCC mapping table" will change more often than the dish coordinates, in particular in ITF and PSI, but we should be able to update the dish coordinates without redeploying software.