Detect ranges for time-space partitioning

What does this MR do?

Another iteration on #220321 (closed): We don't need to specify min_date, max_date specifically anymore and rather check what actual data we have on the instance. This is possible because these partitions are not part of the static database schema anymore but rather managed dynamically (if !34504 (merged) is accepted - this is a dependency).

Note this MR targets the feature branch of !34504 (merged) for convenience. Once the other MR merged, I change to point to master instead.

Does this MR meet the acceptance criteria?

Conformity

• [-] Changelog entry
• [-] Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• [-] Separation of EE specific content