Monotonicity violations were being reported in two locations, once in
the sync service and then later in the worker. Because of recent updates
in the sync service, there's never a case where monotonicity violations
would not be caught first within the sync service. This code path only
triggered within L1 syncing verifiers and caused issues with unintended
timestamp manipulation.