[8.x](backport #41583) x-pack/filebeat/input/entityanalytics/provider/okta: Rate limiting fixes

[mergify]

Proposed commit message

x-pack/filebeat/input/entityanalytics/provider/okta: Rate limiting fixes

- Separate rate limits by endpoint.
- Stop requests until reset when `x-rate-limit-remaining: 0`.

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Discussion

Can be reviewed commit-by-commit.

The reason a new rate.Limiter needs to be created when x-rate-limit-remaining: 0 is that while rate.Limiter allows updating of the rate and burst, it doesn't allow clearing of existing tokens.

Disruptive User Impact

None.

Related issues

• Relates x-pack/filebeat/input/entityanalytics/provider/okta: Rate limiting hangs #40106

  ---

  This is an automatic backport of pull request x-pack/filebeat/input/entityanalytics/provider/okta: Rate limiting fixes #41583 done by Mergify.

[elasticmachine]

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