Wrong HTML output pagination when query parameter `limit` exceeds maximum configuration

[julianzz98]

Describe the bug
When a limit parameter higher than the configured maximum is passed in the request, the response correctly falls back to the maximum allowed value. However, the pagination information in the HTML output still seems to be calculated based on the originally requested (but invalid) limit value.

Steps to Reproduce:

1. Send a request with a limit parameter higher than the configured maximum.
   Example:

   https://localhost:8182/deegree-ogcapi/datasets/BoreholeML_3.1.0/collections/Borehole/items?limit=10000
   

2. Observe that the response only contains 1000 features (the configured maximum).

3. Check the pagination information in the HTML output.

Expected Behavior:
Pagination should be calculated based on the actual applied limit (e.g., 1000), not the originally requested limit (e.g., 10000).

Actual Behavior:

• Only 1000 features are returned per page (as expected).
• Pagination incorrectly shows ~502 pages (calculated for 10000 features per page).
• Correct pagination would be ~5000+ pages (calculated for 1000 features per page).

Desktop (please complete the following information):

• Version: 1.3.9
• OS: Windows/Linux
• Datasource: PostgreSQL/Postgis
• Browser: Firefox, Chrome etc.