BREAKING(testing): replace TimeError exception in favor of built-in error classes in some cases

[iuioiua]

What's changed

Previously, all exceptions within FakeTime threw TimeErrors. Now, some exceptions throw RangeErrors, and TypeErrors, depending on the nature of the error. @throws JSDoc tags have also been added to the documentation.

Motivation

This change was made for two main reasons:

1. Reduce the number of imported symbols required to error-handle FakeTime.
2. Provide more context behind the nature of the errors, via the error class names, and therefore allow errors to be more easily differentiated within FakeTime.

Migration guide

To migrate, when error-handling FakeTime, use the appropriate error class for the given error message (see table below for reference).

- import { FakeTime, TimeError } from "@std/testing/time";
+ import { FakeTime } from "@std/testing/time";

try {
  new FakeTime.restore(NaN);
} catch (error) {
- if (error instanceof TimeError && error.message === "Invalid start") {
+ if (error instanceof TypeError && error.message === "Invalid start time") {
    // ...
  }
}

Error message	Corresponding error class
"Invalid start time"	TypeError
"Time cannot go backwards"	RangeError

Related

Towards #5476

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.48%. Comparing base (2b33b55) to head (d5c597b).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #5550   +/-   ##
=======================================
  Coverage   96.48%   96.48%           
=======================================
  Files         465      465           
  Lines       37772    37772           
  Branches     5580     5580           
=======================================
  Hits        36445    36445           
  Misses       1285     1285           
  Partials       42       42           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[iuioiua]

@KyleJune, does this change seem reasonable to you?

[KyleJune]

@KyleJune, does this change seem reasonable to you?

Seems reasonable to me. I don't have any issues with this change.

[kt3k]

LGTM