[BUG] Stops sharing coordinates can never be clicked: disableClusteringAtZoom defeats spiderfy

What happens

When a trip models several stops at the same place — the common real-world case of leave the bags → check in → the museum inside the hotel → the residents' tour, or any multi-step visit to one building — the map draws them stacked on one pixel. Three of the four can never be clicked, hovered or even seen.

Clustering is supposed to answer this: the plugin keeps children that cannot be separated by zooming in a single cluster and spiderfies them on click. disableClusteringAtZoom={11} switches clustering off wholesale above z11, so that cluster stops existing and the marker stack is left behind with no way in.

Why

leaflet.markercluster/dist/leaflet.markercluster-src.js, _zoomOrSpiderfy:

if (bottomCluster._zoom === this._maxZoom &&
    bottomCluster._childCount === cluster._childCount &&
    this.options.spiderfyOnMaxZoom) {
    // All child markers are contained in a single cluster from this._maxZoom to this cluster.
    cluster.spiderfy();
} else if (this.options.zoomToBoundsOnClick) {
    cluster.zoomToBounds();
}

The spiderfy branch is exactly the same-coordinate case (bottomCluster._zoom === _maxZoom means "no zoom level can split these children"). MapView.tsx sets both spiderfyOnMaxZoom (line ~889) and disableClusteringAtZoom={11} (line ~888), so above z11 the branch is unreachable: no cluster exists to trigger it. Since BoundsController fits a selected day at up to maxZoom: 14, the day view is above the cutoff and the stack is what a user sees.

Suggested fix

Drop disableClusteringAtZoom, or set it to the map's own ceiling (MAP_MAX_ZOOM). maxClusterRadius is in pixels at the current zoom, so ordinary stops still come apart on zoom-in without that option; only the ones that share coordinates stay clustered — and those are precisely the ones that need spiderfy.

Reproduced on current main with a trip holding four stops at one hotel's coordinates.