Picking returning `undefined` on opposite sides of the antemeridian in CV

[ggetz]

What happened?

Identified in #13098, there is an issue where picking is return undefined when picking subsequent times on opposite sides of the antemeridian. It's only apparent in Columbus View.

Reproduction steps

1. Open the testing Sandcastle
2. Set the map mode to CV in the map mode picker.
3. Zoom out a bit so that the edges of the projected map are visible.
4. Mouse over the empty space on the left side of the map. As expected, red markers show up on the right side of the map indicating undefined values returned from the pick.
5. Mouse over the right side of the map (the map itself, not the empty space) in the same areas where where the markers appeared. Unexpectedly, more red markers show up, indicating undefined values returned from the pick.

The issue is also apparent when repeating the steps above but mirroring left and right.

Sandcastle example

Sandcastle

Environment

Browser: All (Identified in Chrome)
CesiumJS Version: Starting in 1.138, if not previous versions
Operating System: All (Identified on MacOS)

[ggetz]

The sandcastle example uses Globe.pick, but this is also reproducible with pickPosition— see #5076.

[mzschwartz5]

Huh, my gut instinct here was that there's some stale node in the TerrainPicker quadtree. But I tried setting the maximum level to 0, so that effectively it's never caching any nodes, and the problem persists. That leads me to believe the TerrainPicker isn't the issue at all, as, with this setting, it's identical to the old terrain picking algorithm.

I also tried hardcoding the scene mode to SceneMode.COLUMBUS_VIEW in TerrainMesh.prototype.pick, in case maybe a stale transform for the wrong mode was being used. That didn't resolve this either.

The fact that this only happens in CV mode and not in 2D mode is perhaps a hint to the root cause, though at the moment I have no further ideas about what that may be.