Add RTCM ARP Logging on non-ZED logging platforms

[PaulZC]

On ZED-based hardware, the code uses the u-blox GNSS library to store the RTCM 1005 / 1006 ARP using setRTCM1005InputcallbackPtr and setRTCM1006InputcallbackPtr

If I'm reading the code right, we would lose this functionality on non-ZED platforms that support logging

Should we parse incoming RTCM centrally, using the semp, and update the ARP there?

Follow newARPAvailable and settings.enableARPLogging for the links

[PaulZC]

I think this issue is still valid. Postcard users may find it useful to have the ARP from 1005 / 1006 included in the SD log files.

If all RTCM arriving over NTRIP Client is passed through a SEMP, extracting the ARP should be ~easy?

@nseidle - should I take a look at this on Monday? Is it worth adding?