Fix usage of ES.CalendarEquals

[justingrant]

TS found a bug in several callers of CalendarEquals. This bug didn't break any tests because it only executed when non-calendar units were equal, but the new code matches the spec.

Also, including the Test262 submodule broke my git repo, so I had to re-clone my local repo from GitHub. When I ran npm install after doing this, there was a one-line change made in package-lock.json. I assume this is OK.

[justingrant]

FYI @12wrigja as you're working on those files over in @js-temporal/temporal-polyfill.

[codecov]

Codecov Report

Merging #1858 (92ae1ea) into main (1cde28d) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main    #1858   +/-   ##
=======================================
  Coverage   94.78%   94.78%           
=======================================
  Files          19       19           
  Lines       10969    10969           
  Branches     1712     1712           
=======================================
  Hits        10397    10397           
  Misses        557      557           
  Partials       15       15           

Flag	Coverage Δ
test262	81.23% <75.00%> (ø)
tests	89.42% <75.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
polyfill/lib/plaindate.mjs	90.26% <100.00%> (ø)
polyfill/lib/plaindatetime.mjs	97.30% <100.00%> (ø)
polyfill/lib/plainmonthday.mjs	87.16% <100.00%> (ø)
polyfill/lib/plainyearmonth.mjs	95.90% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1cde28d...92ae1ea. Read the comment docs.

[ptomato]

Thanks, this is correct. (I'm not sure what caused the diff in package-lock.json; maybe a different npm version?)