Adds tests for Enterprise Search

[picandocodigo]

There are some new entsearch tests in the YAML Elasticsearch tests. They need the creation of two new users and roles. The users are created here as entsearch-user:entsearch-user-password with the role user: and entsearch-unprivileged:entsearch-unprivileged-password with the role unprivileged. The role definitions can be found here.

The build broke for the Ruby stack client and would need to be updated to address these failures. Instead, I'm going to skip those tests and migrate the tests here.

According to the generated report, we are back to (almost) 100% coverage for Serverless.
The three remaining APIs:

• ml.flush_job - We have Investigate why flush_job is failing sometimes #31 for this.
• security.update_api_key - This is a tricky one. I tried adding it to our API key tests, but it was erroring. The docs say: It’s not possible to use an API key as the authentication credential for this API. To update an API key, the owner user’s credentials are required. Our clients authenticate with API key, so I don't know if this would make sense to have this endpoint in the clients, as far as I understand, we can't use this API with API key? 🤷
• tasks.get - is not available on Serverless: [410] api_not_available_exception - Request for uri [/_tasks/] with method [GET] exists but is not available when running in serverless mode

[JoshMock]

I haven't re-added connector APIs to my generator so I can't run these tests locally yet. Have we verified those APIs are ready for 8.15? In any case, the tests look good!

[picandocodigo]

Thanks Josh! The Connectors APIs are currently marked as "beta" in master:
https://www.elastic.co/guide/en/elasticsearch/reference/master/connector-apis.html
They're available in the Ruby stack client and I generated the code to run these tests for Serverless (though I haven't merged them).

Ideally we shouldn't have to skip any tests with this new project, but I added that functionality to the new Ruby runner just in case. If I merge this, does it break the build for JS and others or can those tests be skipped if the APIs are not available?

[JoshMock]

Nope, merge away! I already added skips for those tests.