Describe the bug

We got services with checks configured to run only at certain times, e.g. each morning between 0600 and 0630. Outside of this timeframe, IcingaDB-Web starts showing those services as Overdue, even though it is expected behaviour for those checks not to return any results nor to be run at that moment.

To Reproduce

1. Configure a check to only run within a certain time period
2. See the check being executed and the service view being correct in IcingaDB-Web during that timeframe
3. Wait until the timeframe ends (and a bit longer)
4. See the service becoming Overdue because IcingaDB (not Icinga2 itself, I think) expects it to be executed.

Expected behavior

IcingaDB should honor time periods and not just account for check intervals for inferring Overdue state.

Your Environment

Include as many relevant details about the environment you experienced the problem in.

• Icinga DB Web version (System - About): v1.1.1
• Icinga Web 2 version (System - About): v1.12.1
• Web browser: Edge
• Icinga 2 version (icinga2 --version): v2.14.0
• Icinga DB version (icingadb --version): v1.1.1
• PHP version used (php --version): v7.4.33
• Server operating system and version: RHEL8