#9268: Fix domain values on empty areas

[offtherailz]

Description

The issue #9268 was caused by rangeData (data on the current timeline viewport downloaded) to not have complete priority over domain data, that happened only when the domain values are less than 20.

In fact in this case, the back-end lists all of them, not only the generic interval (startDate--endDate) and the code didn't take into account this use case.

During the investigation we have also found another issue concerning the filter on viewport when the timeline was closed

screencast-bpconcjcammlapcogcnnelfmaeghhagj-2023.10.06-15_15_48.webm

Please check if the PR fulfills these requirements

• The commit message follows our guidelines: https:/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)

• Bugfix

Issue

What is the current behavior?

#9268

What is the new behavior?
Fix #9268

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

[ale-cristofori]

@offtherailz, I tested the PR and it is working as expected. I am going to assign this to a developer for a review. There are still a couple of questions open that do not pertain to this PR

• Understand why sometimes the map centre has wrong coordinates (tried a few times but unable to replicate)
• The timeline has a bug when inserting manually dates/times Timeline - The date/time text editor won't support user keyboard entries if date is higher than current date/time #9754

[tdipisa]

@ElenaGallo please test in DEV once deployed.