[Akamai SIEM] - Fixed pagination logic to use the limit field instead of the offset field

[ShourieG]

Type of change

• Bug

Proposed commit message

The Integration was incorrectly using the `offset` field to determine the pagination logic.
This PR fixes this issue by making use of the `limit` field instead. The documentation
can be found here: https://techdocs.akamai.com/siem-integration/reference/offsetcontext

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

Author's Checklist

• [ ]

How to test this PR locally

Related issues

• Closes [akamai.siem]: Pagination logic causes excessive API requests #16186

Screenshots

[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

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: cc0b43e

cc @ShourieG