Vectra RUX: validate pagination parameters from API responses

[chemamartinez]

Proposed commit message

Validate if fields from API responses that are used for pagination exists and contain valid data before using them for further requests.

Fixes this error where the from query parameter contains garbage after receiving a response without the next_checkpoint field:

"event":{"error":{"code":"400","id":"400 Bad Request","message":"GET https://<>.portal.vectra.ai/api/v3.4/events/detections: {\"detail\":\"The following query parameter(s) are invalid: 2.966648e+06\"}"}}

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.
• I have verified that any added dashboard complies with Kibana's Dashboard good practices

[elasticmachine]

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

[elastic-vault-github-plugin-prod]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[chrisberkhout]

I think it's better to leave out the sample_event.json changes. Only IDs, date, and agent version changed (and not to a new minimum agent version).

Otherwise looks good.

[chrisberkhout]

After a README update to get the reverted sample_event.json content.

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 7506cbc

History

• 💔 Build #29500 failed cff0c01
• 💚 Build #29432 succeeded 716c984

cc @chemamartinez

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

[elastic-vault-github-plugin-prod]

Package vectra_rux - 0.3.1 containing this change is available at https://epr.elastic.co/package/vectra_rux/0.3.1/