[ML] Moves job and trained model management features into Stack Management

[alvarezmelissa87]

Summary

Updates the navigation for Machine Learning pages, moving admin tasks for managing ML jobs and models to a single place inside Stack Management, and leaving exploratory tasks in a consolidated top-level Machine Learning menu.

The available items vary by solution, so that the navigation for an Elasticsearch project, for example, contains a single item for managing trained models.

Stack management menu for classic/observability/security nav

Stack management for search:

Machine Learning menu for Classic nav

Machine Learning menu for Observability

Machine Learning menu for Security

Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
• This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The release_note:breaking label should be applied in these situations.
• Flaky Test Runner was used on any tests changed
• The PR description includes the appropriate Release Notes section, and the correct release_note:* label is applied per the guidelines

Identify risks

Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.

• See some risk examples
• ...

[github-actions]

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

• /oblt-deploy : Deploy a Kibana instance using the Observability test environments.
• run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

[qn895]

@elasticmachine merge usptream

[peteharverson]

Tested latest changes and LGTM 🎉

[elasticmachine]

⏳ Build in-progress

• Buildkite Build
• Commit: 68ced97
• Kibana Serverless Image: docker.elastic.co/kibana-ci/kibana-serverless:pr-204290-68ced972889f

History

• 💚 Build #291210 succeeded da35503
• 💔 Build #290950 failed 600b7f8
• 💚 Build #290858 succeeded 8af34f8
• 💛 Build #290518 was flaky df561f9
• 💔 Build #290485 failed d3f2c99
• 💔 Build #290427 failed 966e180

cc @alvarezmelissa87 @qn895

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 204290 locally