Fix flaky time comparison in storage clean up test
Currently when we insert times into storage_cleanups
we do not insert it with a time zone. This means that the local time is used. The problem is that when we scan it back out into values, UTC is used. This means we end up with an incorrect time. To be consistent, we should eventually change all triggered_at
to be inserted with AT TIME ZONE 'utc'
but until then this test will need a helper to compare just the time components without considering the time zones.
fixes: #3828 (closed)