Add `requestRuleRefreshHash` handling to Cesium layer plugins

[dsuren1]

Description

When request configuration rules are updated at runtime, MapStore creates a fresh requestRuleRefreshHash (uuid) onto every layer whose URL matches a changed rule. The intent is to force the layer to re-fetch tiles/features with the newly resolved headers/params.

The OpenLayers plugins consume this signal, they pair security and requestRuleRefreshHash checks in their update callback and rebuild the source / tile-load function when either changes. The Cesium plugins were not extended with this check, so they currently ignore the hash.

The Cesium layer plugins only invalidate on a security identity change and not when rules changes leaving parameters baked into the underlying Cesium resource go stale

• New tile requests continue to use the old auth headers/params.
• Already-cached imagery keeps displaying, masking the issue until the camera moves.
• The user has to refresh the browser for the new rules to take effect on a 3D map.

Acceptance criteria

• Wire requestRuleRefreshHash handling into the Cesium layer plugins so that a rules-only change triggers a rebuild, alongside the existing security check.
• Check the OL plugins to confirm none have been missed (any newly added URL-based plugin should follow the same pattern), and add the check where applicable.

What kind of improvement you want to add? (check one with "x", remove the others)

• Enhancement
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Other... Please describe:

Other useful information