Import RFC 3339 date-time test vectors from battle-tested parsers across SDKs

[EfeDurmaz16]

Filed from PR #102 review thread (Ludo inline #102 (comment)).

Scope

Import battle-tested RFC 3339 (date-time) test vectors from an established parser's test corpus. Apply the same corpus to every SDK with an expires parser so ACCEPT and REJECT outcomes are mechanically aligned cross-SDK.

Authoritative sources to research

1. RFC 3339 itself (Klyne / Newman): https://datatracker.ietf.org/doc/html/rfc3339
   • Section 5.8: explicit examples (1985-04-12T23:20:50.52Z, 1996-12-19T16:39:57-08:00, etc).
   • Section 5.6: grammar (date-time = full-date "T" full-time).
   • Section 5.7: leap seconds (sec = 60 accepted).
2. ISO 8601:2004 (RFC 3339 is a profile): https://www.iso.org/iso-8601-date-and-time-format.html
3. Battle-tested parsers with their own test corpora:
   • Python `dateutil`: https://github.com/dateutil/dateutil (test/test_isoparser.py is comprehensive).
   • Rust `chrono`: https://github.com/chronotope/chrono (tests/dateutils.rs plus inline #[test] cases).
   • Go `time` stdlib RFC3339 tests: https://github.com/golang/go/blob/master/src/time/format_test.go
   • JavaScript Temporal polyfill (TC39 proposal-temporal): https://github.com/tc39/proposal-temporal (polyfill/test/iso8601/).
   • Java `java.time.OffsetDateTime` JCK / JEP 268 tests.
4. ICU (International Components for Unicode): https://unicode-org.github.io/icu/userguide/format_parse/datetime/

Edge cases the corpus MUST cover

• Leap second (sec=60) at 23:59:60Z (RFC 3339 sec 5.7).
• Lowercase t/z separators (RFC 3339 sec 5.6 allows both; ISO 8601 strict requires uppercase).
• Sub-microsecond fractional precision (7, 8, 9 fractional digits; PHP's %u format only accepts 6).
• Timezone offsets at boundary: +00:00, -00:00, +14:00 (max), -12:00 (min).
• Year 9999 + year 10000 (some parsers explode).
• Calendar validation: Feb 30, Sep 31, year 2000 leap, year 1900 non-leap.
• Month / hour / minute boundary: 00:00:00, 23:59:59 (without leap), 23:59:60 (with leap).

Current parsers to harmonize

• Lua: `lua/mpp/expires.lua`
• PHP: `php/src/Core/Rfc3339Parser.php` (extracted from Challenge.php in PR feat(interop): M1 interop hardening (Token-2022 + symbol-mode + scenarios + RFC conformance + L1-L11 cross-SDK locking) #102)
• Ruby: `ruby/lib/mpp/core/rfc3339_parser.rb` (extracted in PR feat(interop): M1 interop hardening (Token-2022 + symbol-mode + scenarios + RFC conformance + L1-L11 cross-SDK locking) #102)
• Python: `python/src/solana_mpp/_types.py` (and downstream usage)
• TypeScript: `typescript/packages/mpp/src/canonical-codes.ts` / challenge code paths
• Rust spine: challenge parsing

Cross-SDK scope

Tests should assert ACCEPT and REJECT outcomes match across SDKs for each vector. Single PR that touches every language's RFC 3339 test file.

Out of scope

Do NOT propose fabricated vectors. Label as `m2-followup`.