Bin Navara ground corridors set-wide and give corridors glow, pulse and dash

Navara's ground pass cut each corridor into chunks and tested them per
screen cell, so dense corridor sets were slow (10,000 cost about 150 ms a
frame). A corridor set is now cut into pieces along its great circles,
sorted into lon/lat tiles, each with a pyramid of bins listing the
segment runs within its margin; a pixel takes its tile and the finest
bin that covers its reach and tests only those runs. At 10,000 corridors
a frame now takes 11.8 ms still (Cesium 23 ms), at 15,000 17.9 ms. A
pixel corridor's width is measured across the line, so diagonal lines no
longer draw up to 1.4 times wider.

Pixel corridors take three looks, evaluated on the GPU from a time
uniform: Cesium's PolylineGlow falloff (glow), an alpha pulse and the
annotation route's flowing dash. While a shown set pulses or flows the
engine draws continuously, as Cesium did. Traffic's jam lines take the
glow and pulse again and the Directions route its flowing dash and render
hold, so on Cesium both match the drawing before they moved to the
contract pixel for pixel. The contract suite passes on both engines
(Cesium 69/69, Navara 72/72).

scripts/package-boundaries.json

@@ -3577,7 +3577,8 @@
       "src/globe/navara/imagery/pass.js",
       "src/globe/navara/imagery/index.js",
       "src/globe/imagery.js",
-      "src/globe/cesium/imagery.js"
+      "src/globe/cesium/imagery.js",
+      "src/globe/navara/ground/corridors.js"
     ],
     "external": [
       "hls.js",