[ML] Renaming ML API service

[jgowdyelastic]

Addresses the comment from the description of this PR:
We have a bit of a mix of naming: ml, mlApiServices, useMlApiContext() for the same thing

Renames:
useMlApiContext -> useMlApi
ml -> mlApi
mlApiServices -> mlApi
MlApiServices -> MlApi

E.g. we can now use
const mlApi = useMlApi();

Rather than:
const ml = useMlApiContext();
or
const mlServices = useMlApiContext();
or

  const {
    services: {
      mlServices: { mlApiServices },
    },
  } = useMlKibana();

[jgowdyelastic]

/ci

[elasticmachine]

Pinging @elastic/ml-ui (:ml)

[walterra]

LGTM, great to have that consistency now! Just added a comment with a question on some special initialization.

[walterra]

Is there a reason for this specific code or could this be const mlApi = useMlApi()?

[jgowdyelastic]

Yes, this is intentional, this component is shared out from the ML plugin and used in other plugins to warn about ML node availability.
We don't wrap it in a our various contexts and only require that the consuming plugin has http in their kibana context.

[walterra]

Is there a reason for this specific code or could this be const mlApi = useMlApi()?

[peteharverson]

LGTM (also gave each page a quick visual test)

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: d5aca9e

Failed CI Steps

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
ml	4.6MB	4.6MB	-1.7KB

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
ml	78.8KB	78.7KB	-96.0B

History

• 💛 Build #231563 was flaky 5a4be2b
• 💔 Build #231451 failed 638f7f2
• 💔 Build #231381 failed dd55c80
• 💛 Build #231039 was flaky f79a078
• 💛 Build #230865 was flaky f79a078

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

cc @jgowdyelastic