Bug Fixes

[oakdbca]

Move from GET to POST now that OCR Datatable has lots of filtering as it was broken with the url being too long
Various fixes to make the map loading more error tolerant
Clean up unused field out of GeoserverURL model
Update fixture to remove unused field and add correct WMTS version

[sentry]

Bug: A shared cache for WMS and WMTS capabilities can cause a TypeError if both layer types share a geoserver_url with is_capabilities_url set to true.
_{Severity: MEDIUM}

Suggested Fix

Separate the caches for WMS and WMTS capabilities. For example, use two different Map objects, like parsedWMSCapabilities and parsedWMTSCapabilities, to ensure that the parsing logic for each service type uses its own dedicated cache and avoids data structure conflicts.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: boranga/frontend/boranga/src/components/common/map_functions.js#L868-L871

Potential issue: A shared cache, `parsedCapabilities`, is used for both WMS and WMTS
layers that fetch capabilities. If a WMTS layer and a WMS layer are configured to use
the same `geoserver_url` with `is_capabilities_url: true`, a race condition can occur.
The first layer to populate the cache will store its parsed data structure. When the
second layer type attempts to use this cached data, it will try to access properties
that do not exist on the other's data structure (e.g., WMS code accessing
`result.Capability.Layer.Layer` on a WMTS object), leading to a TypeError and causing
the map to crash.

_{Did we get this right? 👍 / 👎 to inform future reviews.}

[xzzy]

Sensitivity Check completed