Create NETWORK_ENABLE_NTP_QUIRKS option

[jxmx]

There is obsolete code in modules/network that tries to force-mangle iptables for NTP purposes. This adds an option to enable that behavior if desired.

[guysoft]

Hey, looks good, but there seems to be a conflict, perhaps because I rebased the previous PR

[jxmx]

Fixed

[guysoft]

Stil conflicting here

[jxmx]

Not sure why that was marked as conflict. I re-saved it. Says it's merge-able again.

[guysoft]

Says its still in conflict.
Note: Thanks for making me look in to it, we will get this in eventually.

It comes from this commit:
0720d5f

@foosel If you have any input and not to busy to add it here it would help.
It says on page 3 of that forum that new rpi installs have fixed this.

Might be also worth to have the NTP comment on top of the config variable.

Prevent NTP updates from failing on RPi3 wifi
While I couldn't reproduce this issue on a current build, apparently
it doesn't necessarily have to happen always and the corresponding
ticket on the rpi bug tracker (https://github.com/raspberrypi/linux/issues/1519) is still
open as well.

Hence this change. As documented at

  https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=141454

and other locations, ntp updates on RPi3 (sometimes?) fail if the
built-in WiFi interface is used. This appears to be the same issue
or at least related to SSH not properly functioning as described
in #294 and also documented in https://github.com/raspberrypi/linux/issues/1519.

A wrong system date of the underlying OS will cause issues with
SSL handshakes, which in turn will produce fatal errors when
attempting to install plugins (see https://github.com/OctoPrint/OctoPrint/issues/1827) or
probably also when updating either OctoPrint or the system itself.
Basically anything that does certificate validity checks will fall
on its face.

Having the Pi properly set its system date is hence crucial for
operation, so we need to make sure ntp can do its job.

This might also affect RPiZeroW - I haven't observed the issue
with a current build there though.

[jxmx]

I do not see this in conflict:

[jxmx]

Regarding Pis, AllStarLink currently has hundreds if not 1000+ Pi appliance installs of Debian 12 bookworm using CustomPiOS and our setup doesn't use iptables or ntpd and there have been no reports of time sync problems. We support Pi 3, 4, 5 and Zero W2s.

[jxmx]

@guysoft I merged in devel with this branch. Are the conflicts clear now?