Populate SearchSelectControl dev setup with a real paginated endpoint

[saknarajapakshe]

Context

From PR review on #2 (feat: Decouple SearchSelectControl from HTTP via SearchService interface):

The dev setup (packages/jsonforms-renderers/dev/main.tsx) currently doesn't wire SearchSelectControl up to a real paginated HTTP endpoint. Reviewers/contributors can't easily exercise the HTTP-backed SearchService implementation without standing up their own backend.

Task

Wire the dev setup to a publicly available, CORS-enabled, paginated API so anyone can run the dev app and test the component end-to-end (loading states, pagination, error handling) without auth or a local server.

Candidate endpoints

API	Pagination params	Auth	Notes
JSONPlaceholder	_page, _limit	No	Classic fake REST API (posts, users, comments); returns X-Total-Count header
SampleAPI	_page, _limit, _sort, _order	No	Built specifically for frontend testing
Mockfly	_page, _limit	No	Supports CRUD, artificial delay (_delay), and error simulation (_status)
Free Dummy API	varies	No	Multiple paginated endpoints (users, orders, products)

Example:

fetch("https://api.mockfly.dev/hub/users?_page=2&_limit=10")

Acceptance criteria

• Dev setup's SearchSelectControl example is backed by a real, publicly reachable, CORS-enabled paginated endpoint (no auth required)
• Works out of the box for anyone cloning the repo and running the dev app
• (Nice to have) Demonstrates loading and error states via the chosen API's delay/error simulation, if supported