Feat(api): Make the existing routes compatible for Peer Review

name: API Issue
about: Report an issue or suggest an improvement related to the backend API endpoints.
title: "[API]: "
labels: "api"
assignees: ''

title: "feat(api): "

🔌 API Issue

Describe the API issue

Optimize the existing record fetch endpoint for peer-review infinite scroll feature.

Upgrade the /next-for-review endpoint to new new parameter like (?many) which responds with default 10 records as response, also update the mediatype filter to accept multiple mediatypes in the parameters.

Optimize the existing api routes for fetching record details by combining them into a single unified api endpoint.

The endpoints concerned for this are: get /record/{record-id} ; get /next-for-review ; get /{recrod-id}/record-url

API Endpoint (if applicable)

get /record/{record-id} ; get /next-for-review ; get /{recrod-id}/record-url

Request/Response examples (if applicable)

Provide examples of the request and response that illustrate the issue.

Expected behavior

A clear and concise description of what the expected API behavior should be.

Additional context

Add any other context about the API issue here.

📌 Follow semantic issue titling convention: <type>(<scope>): <description> (e.g., feat(api): add user registration endpoint or fix(records): handle null values).