Fix spatial Hilbert to use offset of the minimum range key - #2586

Overview

Spatial Hilbert index incorrectly did not offset the keys being encoded by the minimum key in the KeyBounds of the index. Because Hilbert will attempt to figure out the number of bits required to encode values in the given key range it the following exception can be thrown when KeyBounds provided to the HilbertSpatialKeyIndex constructor does not contain minKey = SptialKey(0, 0)

java.lang.IllegalArgumentException: value doesn't fit

However, it is possible that a layer indexed by HilbertSpatialKeyIndex with minKey > SpatialKey(0,0) would not produce this error when writing if the minimum key was large enough to require the same number of bits as the maximum key. This PR will break reading those layers by changing the mapping from stored record index to SpatialKey instance.

It seems unlikely that this bug would have gone unreported if this is was a prevailing case, however there is a way to fix such layers without re-ingesting them.

IF this PR breaks your layer indexed by HilbertSpatialKeyIndex you can fix it by changing the layer metadata keyIndex.properties.keyBounds.minKey to have col = 0 and row = 0.
This value can be find in the JSON file metadata__<layer_name>__<zoom_level>.json in S3, File, and Hadoop attribute stores.

Before:

After:

This will not effect the layer KeyBounds as shown in the TileLayerMetadata[K] but only adjust the KeyBounds used by the HilbertSpatialKeyIndex instance, adjusting it to match new reality.

• docs/CHANGELOG.rst updated, if necessary
  - [ ] docs guides update, if necessary
  - [ ] New user API has useful Scaladoc strings
• Unit tests added for bug-fix or new feature