Ensure MS contains enough information for pointing calibration

The feature has delivered the functionality to add the required OFFSETs into a measurement set when written. This is provided by an interface to Kafka queue that contains commanded and actual positions. it should be noted that even if there are future changes to the contents of the Kafka queue due to architecture or design changes - the work done here still would be able to add the SOURCE OFFSET to the measurement set as the various elements are separated by well defined interfaces.   Some of the outcomes from the child tickets are listed here.   We added a method to MS Writer in realtime-receive-core to write to the pointing table - using a class representing a simplified row in the pointing table (see pointing.py ) We added a test to test_msutils.py to verify the pointing data gets written correctly, and it passes. We updated the documentation with instructions relevant to M1 Mac. See docs/src/installation.rst . Changes have been merged into main (merge request !76 ). We created a tech-debt ticket for a problem we encountered. In the realtime-receive repositories, documentation and helper scripts need to be updated to cater to MacOS & M1 Macs. See YAN-1306. Changes have been merged to the ska-sdp-realtime-receive-processors repository. See merge requests !33 and !34 . Antenna pointing information, including pointing offsets, are written to the pointing table in the measurement set. Pointing data (provided by a Tango device) is read by a Kafka consumer from two topics: a topic for ACTUAL pointings and a topic for COMMANDED pointings. We generate a pointing entry (numpy array) for each antenna at the cadence of the actual pointing, and we extract the corresponding commanded pointing at this timestamp via a cubic spline interpolation (the InterpolatedUnivariateSpline method from SciPy). Rows of pointing data are produced in mswriter_pocesssor.py , then transferred to src/realtime/receive/core/msutils.py where it is written to the measurement set. In the ms pointing table, commanded pointings are written to the TARGET column, actual pointings are written to the DIRECTION column, and the offset (ACTUAL minus COMMANDED) is written to the SOURCE_OFFSET column.