Adapt testing/benchmark to okta-aws-cli

[carsonip]

Motivation/summary

Use okta-aws-cli with elastic-observability

Checklist

• Update CHANGELOG.asciidoc
• Documentation has been updated

For functional changes, consider:

• Is it observable through the addition of either logging or metrics?
• Is its use being published in telemetry to enable product improvement?
• Have system tests been added to avoid regression?

How to test these changes

make auth apply to create infra. make destroy or make auth destroy (if credentials expired) to destroy infra.
~/.aws/credentials should be updated.

Related issues

Fixes #15511

[mergify]

This pull request does not have a backport label. Could you fix it @carsonip? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-7.17 is the label to automatically backport to the 7.17 branch.
• backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit.
• backport-9./d is the label to automatically backport to the 9./d branch. /d is the digit.
• backport-8.x is the label to automatically backport to the 8.x branch.

[1pkg]

nice

[v1v]

We need to use the elastic-okta-awscli - the only CLI available for some Elastic employees. The current elastic-observability should work with that tool.

We can sync up and discuss this if needed