fix: correct UPS and USPS time parsing

[egg-]

Summary

Fixes two time-parsing bugs in the UPS and USPS couriers, both originally reported in #35.

Background

@aldin-alagic opened #35 in December 2022 with fixes for exactly these two bugs. It sat unreviewed, and by the time v3 landed the sources had moved from lib/ to src/, so the patch no longer applied. The bugs were still there — the v3 rewrite carried them over unchanged, and the comparison I ran against v2 could not catch them because both versions were wrong in the same way.

Changes

• UPS — UPS reports a 12-hour clock as 10:53 P.M., but the format string read it as HH:mm. The meridiem was ignored, so every afternoon event was recorded twelve hours early. Seven of the twelve activities in the recorded fixture are P.M., so this was wrong more often than it was right. dayjs's A token only matches PM, not P.M., so the periods are stripped before parsing with h:mm A.
• USPS — runs of whitespace inside the date cell are collapsed before parsing, and the format list now also accepts a space after the second comma. The page has shipped several layouts of this string over the years.
• Added a regression test for each. The existing sweep only asserted that a timestamp parsed at all, which a twelve-hour error passes cleanly.

Key files

src/courier/ups.ts, src/courier/usps.ts, test/checkpoint-time.test.ts

Rollout / Follow-up

Folded into the unreleased 3.0.0 rather than a patch release, since v3 has not been published yet.

Closes #35.

Risks

UPS timestamps that consumers stored from earlier versions will not match what this returns for the same shipment — the old values were simply wrong for afternoon events.

Verification

Reverting either fix makes the new tests fail, which is how the UPS bug was confirmed rather than assumed.