[FEATURE] Alerts API Enhancements

Is your feature request related to a problem?
The current challenge involves users being unable to view all alerts in the Alerts page when dealing with a large volume of generated data/Alerts. Despite the backend accurately producing all alerts, some are not visible in the UI. To remedy this, it is essential to implement proper pagination in the UI.

What solution would you like?
To alleviate the pagination challenge on the UI, a backend modification is proposed for the /alerts API. Currently, alerts are generated as per parameters such as detectorId, detectorType, severityLevel, alertState, table (Table params include: sortOrder, sortString, missing, size, startIndex, and searchString). To enhance efficiency, the suggestion is to adapt the backend to return all the alerts collectively. This modification would consolidate the data, allowing the frontend to implement pagination more effectively. With this approach, pagination efforts can be concentrated on the UI side, simplifying the user experience when navigating through extensive alerts.

What alternatives have you considered?
A clear and concise description of any alternative solutions or features you've considered.

Do you have any additional context?
Similar to Findings API enhancement -> #795

Start by tracing the /alerts API and the Alerts page, comparing the existing detector, severity, state, table, and search parameters with the pagination behavior. Use issue #795 as the related reference. Done means the API and UI can expose and navigate the complete alert set without missing alerts when volumes are large.