[ENG-58761]:Migrate detect API to Alerts

[rakhimundhada15]

Problem Description

The Detection API endpoints are deprecated and will be decommissioned on September 30th, 2025. The Alerts api is provide Legacy concepts, so migrated to Alerts API.

Solution Description

Added support to collect detection data using the Alerts API. The existing Detection API code can be removed if it begins to fail or once it is officially(i.e. September 30th, 2025) deprecated.
To retrieve alert details, use the following APIs:

1. Query Alert IDs
   GET /alerts/queries/alerts/v2
   Use filters such as project:epp and created_timestamp to identify relevant alert IDs.

2. Fetch Alert Details
   POST /alerts/entities/alerts/v2
   Use the retrieved alert IDs to get detailed information about each alert.

Acceptance Criteria for Contributors

1. Alerts API Integration
2. Existing Detection API code should remain functional but be clearly marked as deprecated.
3. If the Detection API begins to fail (e.g., returns errors or is unreachable), it should be safely removed or bypassed without breaking the system.
4. Added unit tests to cover the new Alert API integration.

[al-cibot]

CI Service Job Number 1099 Logs - SUCCESS

alps ci job-logs --organization alertlogic --repository paws-collector --job-num 1099 -g

Stages Run:

• PR Test

[al-cibot]

CI Service Job Number 1100 Logs - SUCCESS

alps ci job-logs --organization alertlogic --repository paws-collector --job-num 1100 -g

Stages Run:

• PR Test

[rakhimundhada15]

build-collector-crowdstrike

[al-cibot]

CI Service Job Number 1101 Logs - SUCCESS

alps ci job-logs --organization alertlogic --repository paws-collector --job-num 1101 -g

Stages Run:

• build-collector-crowdstrike
• file_packager_bb9e31