feat!: consolidate storage schemas and add Redis provider (MAPCO-11262)

[almog8k]

Question	Answer
New feature	✔
Breaking change	✔

What

Consolidates the deletion schemas around a single storageProvider discriminator, and adds Redis as a storage provider so a layer's Redis-backed tile cache can be deleted through the same shapes as FS and S3.

Why

Tile deletion and stored-resource deletion each handled providers their own way — tiles keyed on sourceProvider, stored resources on an intersection with storageSchema. Adding Redis to both would have meant duplicating that logic twice. Instead there is now one discriminator, with each provider's params composed from small reusable pieces.

Changes

• StorageProvider (FS | S3 | REDIS) becomes the storage discriminator, replacing SourceType. It is deliberately not spread from SourceType, which also contains GPKG — a source format rather than a storage backend, and one that no storage schema accepts.
• redisStorageSchema joins storageSchema, located by a Redis key prefix.
• Tile schemas split into composable parts: tileRangesSchema (which tiles) and tilesInfoSchema (tilesRelativePath + fileExtension, meaningful only for path-based stores), combined as tilePyramidSchema.
• Both deletion param schemas are now discriminated unions over storageProvider with an S3 / FS / Redis member each, and each member is exported as its own type.
• The two Redis shapes share a base carrying the prefix plus an optional delaySeconds, to wait out a mapproxy reload before the keys are removed. Both are .strict(), so path-store fields such as paths are rejected outright rather than silently stripped — for a key-value store the prefix is the locator.
• Cache_Deletion job type and cache-deletion task type added.

Also included: an import-cycle fix

constants/export/constants.ts imported pickEnum through the utils barrel, which pulls in layer.utils → the schemas barrel while constants is still initializing. As a result 9 of 11 schema modules threw Cannot access '<x>' before initialization when imported directly — only the package entry point worked, because it happens to load utils first. It now imports the module directly, matching what constants/core/constants.ts already did. All 11 modules load.

This is why the package currently has no schema tests: a spec importing any schema module hits the cycle.

Breaking changes

• Tiles deletion discriminator renamed: sourceProvider → storageProvider
• Field renamed: tilesPath → tilesRelativePath
• tilesDeletionParamsSchema / TilesDeletionParams moved from the core scope to deletion
• Removed: tilesDeletionParamsBaseSchema, deleteStoredResourcesParamsBaseSchema

[github-actions]

Hi it is me, your friendly bot helper! 👋
I've packed this commit for you 😊
You can install it like this:

{
  "dependencies": {
      "@map-colonies/raster-shared": "https://ghatmpstorage.blob.core.windows.net/npm-packages/raster-shared-a022e3faf8e92677e7990d96437cb3d41a2fa685.tgz"
  }
}

The link will expire in a week ⌛