Dynamic Filter Widget: "APPLY DIMENSION" to update Time and Elevation #12267

[rowheat02]

Description

This PR adds Apply Dimension as an optional target for interactions. Can connect to update the layer time and elevation. If a timeline exists, a different global node "MapTime" to control currentTime of timeline

Here are the conditions applied for Apply Dimension

• Maptime(target) can only be connected alone; other targets can not be connected on the same filter. This is done to make consistent reerse sync.
• When range is enabled in timeline, mapTime connected widget will be disabled
• An apply dimension node can only be connected when selection mode is "Single"
• For elevation, the value field must be numeric, and for time, it must be datetime/date

Demo for Map:

Screen.Recording.2026-05-07.at.20.42.18.compressed.mp4

Demo for Dashboard

Screen.Recording.2026-05-07.at.20.57.23.compressed.mp4

Please check if the PR fulfills these requirements

• The commit message follows our guidelines: https://github.com/geosolutions-it/MapStore2/blob/master/CONTRIBUTING.md
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (check one with "x", remove the others)

• Enhancement

Issue

What is the current behavior?

#12267

What is the new behavior?

The user can connect the dimension update node of the layer(time and elevation)

Breaking change

Does this PR introduce a breaking change? (check one with "x", remove the other)

• Yes, and I documented them in migration notes
• No

Other useful information

[offtherailz]

I still need to check the code. Make sure to design the application with best practices. I see a lot of code and ifs that looks to be hard to maintain

• Conditional Visibility for "+" Button: it should show when at least one additional event can be added. In the stile case, when userDefined style is selected. In case of apply dimension it only appears when a dimension can actually be applied. This prevents users from clicking an action that has no effect.
• Option vetical/horizonal makes no sense on slider (or still not supported) disable it.
• Implement backward compatibility for missing attribute types.
• See comments inline

[offtherailz]

Logic for dimension should be isolated somehow. Interaction row component can not contain the logic for every possible target.
Or we have different components for different actions to do (that maybe share a basic graphic component, that allows to place the row icon, text, tooltops, components etc..., if makes sense), or a logic should be in the container using component. This depends of course on the items.