[Logs UI] Add ML module setup hook

[weltenwort]

⚠️ This is just a draft for inclusion in a larger PR. It includes commits from the prior unmerged PR #42931.

Summary

This sketches how the ML module setup API can be called for the log analysis module (defined in #42872) using the new overrides enabled by #42946.

[elasticmachine]

Pinging @elastic/infra-logs-ui

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request

[elasticmachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request

[jasonrhodes]

I'm pulling this in now to review now that the module PR is merged and I can test it. Also this comment review should make the infra-logs-ui team review request go away...

[Zacqary]

How is this hook expected to be used? Is it something like this?

const [setupMlModule] = useLogAnalysisJobs();

return <button onClick={setupMlModule}>Create ML Job</button>

[Kerry350]

@Zacqary Pretty much, yep, useLogAnalysisJobs() is already being used in the page component for things like checking the job status. This should be extended to now make use of setupMlModule and setupMlModuleRequest too. Those can be passed directly as props to the setup screen component, <AnalysisSetupContent />, from the page component. No need to call the hook again.

Behind the scenes this uses useTrackedPromise which is used in quite a few places now for data fetching with hooks.setupMlModule will execute the request itself, and setupMlModuleRequest will provide you with state to see if the request is saving / loading.

What I'd recommend is not exporting the setupMlModuleRequest variable directly from the hook (it is at the moment as I needed to satisfy the build and not have variables that were defined but not used). But instead setup another memoized variable, like with the job status in the same hook, and export that variable. E.g.:

const isSettingUpMLModule = useMemo(() => setupMlModuleRequest.state === 'pending', [
    setupMlModuleRequest.state,
  ]);

Just like the job status check. This will provide you with the ability to disable the save button and so on.

[jasonrhodes]

We're going to close this and move forward with the PR that @Zacqary opened off of this branch (#43413), since that PR includes some fixes and tweaks of this work.