[kbn/es] add support for --ready-timeout

[spalger]

We've been getting reports of kbn/es causing problems for people who are using custom data directories. It seems this is caused by two things:

1. the _autoRetry function in the NativeRealm class wasn't slowing down for subsequent retry attempts and instead always retrying after 1 second, meaning that we would exhaust our 10 retries for cluster state after about 10 seconds.
2. the timeout can't be customized, and wasn't explitict before, but was a side effect of how many attempts were allowed.

To fix this I moved the ready check out of NativeRealm (didn't feel like the right place for it, and I had new config to plumb), updated it to respect a timeout, and then added readyTimeout/--ready-timeout and skipReadyCheck/--skip-ready-check options.

[elasticmachine]

Pinging @elastic/kibana-operations (Team:Operations)

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: 96fbcf1
• Storybooks Preview
• Webpack Bundle Analyzer

Metrics [docs]

✅ unchanged

History

• 💚 Build #25995 succeeded 7179bfa
• 💔 Build #25955 failed cf1a83383794e6bbf51bcfef0d8fe26389b7a287
• 💔 Build #25753 failed adf642e4fb26b29948f5fd6e94221cac3c635a53

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[kibanamachine]

💔 Some backports could not be created

Status	Branch	Result
✅	8.0
✅	8.1
❌	7.17	Backport failed because of merge conflicts You might need to backport the following PRs to 7.17: - Support for superuser not having write access (#123337)

How to fix

Re-run the backport manually:

node scripts/backport --pr 126217

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation