Tests rely on time changing

[ThisIsMissEm]

Currently I'm seeing quite a high rate of test failures on WatchOS for what appears to be a failure related due to access token expiry not being as expected. The tests that use AsyncStream<String>.makeStream() tend to rely on time changing in a predictable manner, such as @Test func tokenExpiredAfterUseRefresh, which seems to not always be the case.

I'm wondering if we could actually substitute the Token for these tests with one where we can control whether the token is expired or not?

That would decouple us from any system time weirdness whilst still testing what we want to test: given an access token that starts out valid, but then expires, what are the requests that happen?

[ThisIsMissEm]

An example failure is:

Test run started.
Suite AuthenticatorTests started
Suite GoogleTests started
Suite MastodonTests started
Suite GitHubTests started
Suite BlueskyTests started
Suite DPoPSignerRequestTests started
Suite DPoPSignerTests started
Suite PKCETest started
Suite WellKnownTests started
    ✔ testAppResponseDecode() (14.372 seconds)
    ✔ tokenValidationFailure() (14.373 seconds)
    ✔ appResponseDecode() (14.378 seconds)
    ✔ issuingServerMismatch() (15.907 seconds)
    ✔ customHashFunction() (15.744 seconds)
    ✔ serverMetadataLoad() (18.577 seconds)
    ✔ clientMetadataLoad() (18.577 seconds)
    ✔ testOAuthResponseDecode() (18.739 seconds)
    ✔ protectedResourceMetadataDecode() (18.631 seconds)
    ✔ manualAuthenticationWithSuccessResult() (19.484 seconds)
    ✔ expiredTokenRefreshFailing() (19.624 seconds)
Suite BlueskyTests passed after 19.629 seconds
Suite GitHubTests passed after 19.630 seconds
Suite MastodonTests passed after 19.630 seconds
    ✔ manualAuthenticationWithFailedResult() (19.625 seconds)
    ✔ basicSignature() (19.323 seconds)
    ✔ overwritesAuthorization() (19.323 seconds)
    ✔ invalidRequest() (19.323 seconds)
    ✔ withoutParameters() (19.323 seconds)
    ✔ missingTokenHashThrows() (19.323 seconds)
Suite PKCETest passed after 19.631 seconds
Suite GoogleTests passed after 19.919 seconds
Error: Recorded an issue (Expectation failed: (events1 → ["login load", "refresh", "REFRESH", "login save", "REFRESHED", "request", "***", "checkpoint"]) == (expected1 → ["login load", "request", "*** SOON", "checkpoint"]))
    ✔ testInitialLogin() (18.799 seconds)
Suite WellKnownTests passed after 20.510 seconds
    ✔ "Correctly constructs the JWTParameters" with 5 test cases (20.204 seconds)
    ✔ unauthorizedRequestRefreshes() (20.367 seconds)
    ✔ authorizationResponseAfterInvalidRequestError() (20.368 seconds)
    ✔ resourceResponseWWWAuthInvalidRequest() (20.368 seconds)
    ✔ authorizationResponseSuccess() (20.368 seconds)
    ✔ manualAuthentication() (20.205 seconds)
Suite DPoPSignerTests passed after 20.513 seconds
    ✔ authorizationResponseAfterDPoPError() (25.824 seconds)
    ✔ requestsAgainstDifferentOrigins() (25.824 seconds)
Suite DPoPSignerRequestTests passed after 25.969 seconds
Error: Recorded an issue (Expectation failed: (events2 → ["request", "***", "checkpoint"]) == (expected2 → ["login load", "refresh", "REFRESH", "login save", "REFRESHED", "request", "***", "checkpoint"]))
Error: tokenExpiredAfterUseRefresh() (25.900 seconds) 2 issue(s)
Error: Suite AuthenticatorTests failed after 26.048 seconds with 2 issue(s)
Testing started
Error: Process completed with exit code 65.

[ThisIsMissEm]

The fix I ended up with was just to make that test run longer, which isn't ideal, but works: b81a754