okta: increase API response limit

[efd6]

What does this PR do?

This increases the limit for the number of results returned in an API response from okta. This allows more responses to be obtained within the API rate limits.

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.

Author's Checklist

• Should this be made a user facing option defaulting to 1000?

How to test this PR locally

Related issues

• Closes [okta] Increase 'limit' value to reduce number of requests #2776.

Screenshots

[elasticmachine]

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
[](https://ci-stats.elastic.co/app/apm/services/beats-ci/transactions/view?rangeFrom=2022-03-09T03:34:04.332Z&rangeTo=2022-03-09T03:54:04.332Z&transactionName=BUILD Ingest-manager/integrations/PR-{number}&transactionType=job&latencyAggregationType=avg&traceId=78096ac80a6747e22fed209746b93419&transactionId=1fa0d19ce41fb96c)

Expand to view the summary

Build stats

• Start Time: 2022-03-09T03:44:04.332+0000

• Duration: 12 min 9 sec

Test stats 🧪

Test	Results
Failed	0
Passed	12
Skipped	0
Total	12

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[marc-gr]

LGTM, just regarding:

Should this be made a user facing option defaulting to 1000?

I am good having it as a hard coded value as far as it does not affect performance in the general case. But exposing it could add flexibility if some users face issues with it I guess.

[efd6]

We can always add a config option in the future if someone asks for it; harder to take it away if it causes problems.