Mid.CBF and SPFRx Implement ADR-32 DISH ID

  DISH ID is used in virtually all components of the M&C software and is embedded in the digitized data flowing through the signal chain.  If implemented early, this is a small change that affects many components. If we continue using numeric-only Dish ID, user interfaces and other interface software will need to be updated later when the Meerkat antennas are integrated, i.e. when  the bulk of M&C software has been developed, integrated and released. 

The Mid.CBF MCS has been updated  to use the correct DISH ID format. The software has been modified to take a DISH ID mnemonic instead of the previous integer. The changes are documented here: https://gitlab.com/ska-telescope/ska-mid-cbf-mcs/-/merge_requests/110 The Mid.CBF MCS is not backwards compatible with the old DISH ID integer and will remain on a branch until other teams are ready to integrate.  A C++ library to translate between the DISH ID mnemonic to the binary format specified in https://jira.skatelescope.org/browse/ADR-32 has been implemented and unit tested here: https://gitlab.drao.nrc.ca/digital-systems/software/libraries/dish-id-utils The Mid.CBF SPFRx has been updated to use the correct DISH ID format - a DISH ID device property has been added to the SPFRx controller. The SPFRx controller writes the DISH ID to the SPFRx packetizer, which uses the Dish-ID-Utils library to translate the mnemonic to binary and write the mnemonic into firmware. The SPFRx controller changes are here: https://gitlab.drao.nrc.ca/digital-systems/ska-spfrx/software/applications/ska-mid-spfrx-controller-ds/-/merge_requests/37,  and the SPFRx packetizer changes are here: https://gitlab.drao.nrc.ca/digital-systems/ska-spfrx/software/applications/ska-mid-spfrx-packetizer-ds/-/merge_requests/21 The BITE engineering console has been modified to take the DISH ID as a configuration parameter in the correct mnemonic format. The changes are here:  https://gitlab.com/ska-telescope/ska-mid-cbf-engineering-console/-/merge_requests/63  (CIP-1178) The scope expanded for the second half of the story  CIP-1178  - the sanity check against the DISH ID recorded in the dish packets. It has been concluded that a better solution for pulling the DISH ID from the data stream is to get it from the Wideband Input Buffer IP block (and not from the Wideband State Count IP block as originally thought). However, this IP block does not currently have a control Tango device server, therefore this device will need to be implemented, tested and integrated. Follow up stories to complete this work are here:  https://jira.skatelescope.org/browse/CIP-1254   https://jira.skatelescope.org/browse/CIP-1255 .  Tests have been modified to use the DISH ID mnemonic. All tests are passing including MCS, SPFRx unit tests and BITE engineering console tests. See passing tests in linked merge requests.