globe.cartographicLimitRectangle can't be unset

[lilleyse]

If you try setting globe.cartographicLimitRectangle to undefined after it has previously been set, it will crash.

Sandcastle

@likangning93 any ideas?

[likangning93]

The shipped Sandcastle demo treats the "deactivation" case as Rectangle.MAX_VALUE, which is default.
Under-the-hood GlobeSurfaceTileProvider always checks tiles against the limiter rectangle but only modifies shaders for terrain tiles that intersect, so the default of Rectangle.MAX_VALUE shouldn't cause any shader modification.

I think it's the right level of abstraction to modify the setter in Globe.js so setting undefined percolates a Rectangle.MAX_VALUE down.

[lilleyse]

That approach makes sense. Also cartographicLimitRectangle seems to be missing documentation - #6987 (comment). It would be good to fix that too.