fix: temporal pagination tests follow TS 104-176 clause 6.4.7.3

Ken Zangelinrequested to merge
fix/temporal-pagination-104-176 into develop

The 020_13 / 020_14 / 021_15 / 021_16 families tested the old GS CIM 009 v1.x clause 6.3.10 binding: 206 Partial Content + Content-Range, with a broker-wide total instance cap cut at attribute boundaries. TS 104-176 clause 6.4.7.3 replaces that mechanism entirely:

  • status is always 200; page pointers are Link header link-values with rel="intervalafter" (the page holding LATER Attribute timestamps) and rel="intervalbefore" (EARLIER) — note the relations are time-oriented, so they swap sides between ascending (firstN) and descending (lastN) pagination
  • the page limit applies per Attribute: firstN (ascending), lastN (descending), offsetN to select the page
  • there is no total cap and no attribute-boundary cut: unsynchronized attributes paginate independently (020_14 now asserts exactly that)

New keywords: Check Temporal Pagination Link / ... Link Absent (AssertionUtils); firstN/offsetN plumbed through the temporal consumption keywords. 021_16 drives pagination through temporalQ.lastN in the POST query body (new fixture entity-operations-paginated-query).

Also covered: firstN+lastN together is contradictory → 400.

021_03 and 020_05 needed no changes — they already expected 200 and fail only against brokers still implementing the v1.x binding.

Merge request reports