Implement overlapping timespans incompatibility check

[jonathan-mayer]

Issue

Currently the user can set the upscale and downscale periods to overlap, which causes one to be preferred. We want to avoid this priority system.

Problem to solve

There needs to be a check that checks for overlapping timespans between the upscale periods and downscale periods.

Further details

Good Luck

Proposal

Add a check in the checkForIncompatibleFields method of the Layer type, that check for overlapping timespans between upscale and downscale periods.
The check should be able to check for incompatibilities between absolute timespans, relative timespans and between relative and absolute timespans.
It also needs to interpret different timezones, this could propose a bigger issue because of the weekday span on relative timespans.

Who can address the issue

Go Dev

Other links/references

[jon4skl]

@jonathan-mayer @JTaeuber Can one of you please send me the docs about the relative and absolute time again? Just put it in the comments here. Thanks

[JTaeuber]

Format

Reoccurring/Relative Time

<weekday_from>-<weekday_to> <time_from>-<time_to> <timezone>

e.g.

Mon-Fri 07:30-20:30 Europe/Berlin

Absolute Time

<RFC3339_TIME_FROM> - <RFC3339_TIME_TO>

e.g.

2024-07-29T08:30:00Z - 2024-07-29T16:00:00+02:00

[jonathan-mayer]

I had another long look over this today. The only way I see to implement this is complex, hard to understand and relatively compute intensive. We already decided this one is not too important, which is why it's been open for so long. I think we should evaluate/discuss if this is still worth implementing/fixing the version on the old branch.

[jonathan-mayer]

If this gets implemented relative timespans should be refactored with it