Fix incorrect ATP time-range assertions

[albertoramosmonagas]

What type of PR is this?

Add one of the following kinds:

• correction
• tests

What this PR does / why we need it:

This PR fixes incorrect ATP validation steps for time interval coverage in Predictive Connectivity Data.

The current ATP steps wrongly assume that each returned interval must be strictly contained within the requested time range. However, according to the specification, the returned intervals must fully cover the requested time range, which means:

• the first interval may start before the requested start time, and
• the last interval may end after the requested end time.

This PR updates the affected ATP checks so that they validate coverage semantics instead of boundary containment, aligning the tests with the API specification and avoiding false negatives in compliant implementations.

Which issue(s) this PR fixes:

Fixes #45

Special notes for reviewers:

This PR does not change API behavior. It only corrects ATP validation logic so that it matches the interval coverage semantics defined in the specification.

Changelog input

 release-note
Fix ATP time-range validation in Predictive Connectivity Data to check interval coverage semantics instead of strict interval containment.

Additional documentation

This section can be blank.

docs

[github-actions]

🦙 MegaLinter status: ✅ SUCCESS

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ ACTION	actionlint	2		0	0.01s
✅ API	spectral	1		0	1.73s
✅ GHERKIN	gherkin-lint	1		0	0.39s
✅ REPOSITORY	git_diff	yes		no	0.01s
✅ REPOSITORY	secretlint	yes		no	0.73s
✅ YAML	yamllint	1		0	0.49s

See detailed report in MegaLinter reports

MegaLinter is graciously provided by