[Datahub][API form] Fix OGC API default limit

[cmoinier]

Description

This PR fixes an unwanted behavior on the OGC API form.
As specified in the OGC API features, the limit parameter has a default value of 10.

Despite being an optional parameter, it appears that it still limits the returned items to 10 if no limit is specified, see for instance : https://mel.integration.apps.gs-fr-prod.camptocamp.com/data/ogcapi/collections/pav_etat_parc/items?f=json

This PR sets a default limit to -1 to ensure all items are returned if no limit is set.
/!\ The limit input does not display -1 to avoid confusion for the user.

Quality Assurance Checklist

• Commit history is devoid of any merge commits and readable to facilitate reviews
• If new logic ⚙️ is introduced: unit tests were added
• If new user stories 🤏 are introduced: E2E tests were added
• If new UI components 🕹️ are introduced: corresponding stories in Storybook were created
• If breaking changes 🪚 are introduced: add the breaking change label
• If bugs 🐞 are fixed: add the backport <release branch> label
• The documentation website 📚 has received the love it deserves

[github-actions]

Affected libs: ui-elements, feature-catalog, feature-record, feature-router, feature-search, feature-map, feature-dataviz, ui-catalog, ui-search,
Affected apps: metadata-editor, datahub, demo, webcomponents, map-viewer, search,

• 🚀 Build and deploy storybook and demo on GitHub Pages
• 📦 Build and push affected docker images

[Angi-Kinas]

Thanks for the fix @cmoinier!
When you removed the 'only' in the e2e-test, it's good to go 👍