Don't alter system timekeeping

[mfeit-internet2]

Per Doug White at Cal Tech:

We recently upgraded all of our test nodes to Perfsonar 5.1.4. After discovering that tests between some of the nodes were failing we determined it was due to “time” not being synchronized. Further investigation determined that the PerfSonar Installation process (curl -s https://downloads.perfsonar.net/install | sh -s - toolkit) had disabled chronyd. It was enabled and running prior to the install and afterward it was still running but had been disabled. As a result, chronyd would not reload after the next reboot.

We have a simple work-around in place as we just issue a “systemctl enable chronyd” immediately following the the software installation so this is not an urgent matter. We thought we would call it to your attention however, in case this is something that can be addressed in a future release.

The toolkit packaging is running configure_ntpd on install. Given that ntpd is deprecated on every platform we support, I think it's time to get out of the business of dictating what manner of time sync is used or enable to Chrony if there isn't already a site-specific config for it.

[mfeit-internet2]

This has been partially taken care of for 5.2.0 only by disabling the configuration of NTP.

The code that does it has a lot of tentacles and needs to be removed carefully. To that end, it has been left in place to avoid breaking anything while 5.2.0 is in beta. Removal should be slated for 5.3 (not 5.2.1 since it's not technically a bug fix).

[laeti-tia]

We have another problem with 5.2.0-beta and timekeeping on some Debian and Ubuntu systems. Our dependency to ntp is generating a conflict at least on Debian-12. I think we should depend on time-daemon instead.