Implements pagination and unread-only filter options to notifications/all endpoint

[GPortas]

What this PR does / why we need it:

Review #11851 first.

The user notifications endpoint has been enhanced with new optional query parameters to allow for more specific and
efficient data retrieval.

1. Filter by Unread Status

You can now fetch only unread notifications by using the onlyUnread boolean parameter.

• onlyUnread: (Optional, boolean) When set to true, the API will only return notifications that the user has not
  yet marked as read.

Example:

curl -H "X-Dataverse-key:$API_TOKEN" "$SERVER_URL/api/notifications/all?onlyUnread=true"

2. Pagination Support

Pagination is now supported through the limit and offset parameters, allowing you to retrieve notifications in smaller,
manageable chunks.

• limit: (Optional, integer) Specifies the maximum number of notifications to return.

• offset: (Optional, integer) Specifies the number of notifications to skip before starting to return results.

Example (Retrieve notifications 11 through 20):

curl -H "X-Dataverse-key:$API_TOKEN" "$SERVER_URL/api/notifications/all?limit=10&offset=10"

Which issue(s) this PR closes:

• Closes Add pagination and unread-only filter options to notifications/all endpoint #11852

Suggestions on how to test this:

Described above

Does this PR introduce a user interface change? If mockups are available, please link/include them here:

None

Is there a release notes update needed for this change?:

Yes, attached

[coveralls]

coverage: 23.558% (+0.008%) from 23.55%
when pulling 80446e7 on 11852-notifs-api-pagination-unread
into 8bb9161 on 11804-notifs-api-ext.

[github-actions]

📦 Pushed preview images as

ghcr.io/gdcc/dataverse:11852-notifs-api-pagination-unread

ghcr.io/gdcc/configbaker:11852-notifs-api-pagination-unread

🚢 See on GHCR. Use by referencing with full name as printed above, mind the registry name.