Verified - ntpd ignores the year part of refclock timestamps

[Trevor N.]

	It's not necessary to use refclock_process() if the driver creates
its own l_fp timecode timestamp and uses refclock_process_offset(). I
was considering removing refclock_process() when I added the rollover
workaround to the trimble driver, but then I read this:
https://bugs.ntp.org/show_bug.cgi?id=417
Where the reasoning behind clock_panic and not using the year in
refclocks is touched on.