[AI Infra] View Chat Experience setting and documentation section requires all privileges

[KodeRad]

Summary

Implements: https://github.com/elastic/ml-team/issues/1755
Follow up to: #244532

The goal of this PR is to make Chat Experience visible only for users who have all privileges. This is Agent and at least one Classic Assistant.

• AI Agent card in Selection modal is now disabled based on user's capabilities to manage agents, not only view them
• DocumentationSection is now displayed only if Chat Experience is present and Agent is chosen

To test it you have to activate feature flag in kibana.dev.yml

feature_flags.overrides:
  aiAssistant.aiAgents.enabled: true

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
• Review the backport guidelines and apply applicable backport:* labels.

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
• ...

[elasticmachine]

Pinging @elastic/ml-ui (:ml)

[elasticmachine]

Pinging @elastic/appex-ai-infra (Team:AI Infra)

[jgowdyelastic]

nit, capabilities could be extracted on line 40. just to make this code a bit more readable.

  const {
    services: {
      spaces,
      application: { capabilities },
    },
  } = useKibana();

[KodeRad]

Good thought! Improved here c43c070

[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!)

[jgowdyelastic]

Code LGTM
I added one code clean up comment

[spong]

Thanks for this fix @KodeRad! This fixes the corner case where the user enables the FF, then the Agent experience, then removes the feature flag, at which point the app would return to the default chat experience but this UI would still show.

[spong]

Docs visibility permissions update LGTM -- thanks @KodeRad!

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: b1434f6
• Kibana Serverless Image: docker.elastic.co/kibana-ci/kibana-serverless:pr-246311-b1434f66ce1a

Failed CI Steps

• FTR Configs #59

Test Failures

• [job] [logs] FTR Configs #59 / EPM Endpoints installs and uninstalls all assets installs all assets when installing a package for the first time should have created the correct saved object

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
aiAssistantManagementSelection	89.5KB	89.5KB	+8.0B
genAiSettings	55.7KB	55.9KB	+240.0B
total			+248.0B

History

• 💔 Build #373335 failed fc019a0
• 💔 Build #373189 failed c43c070

cc @KodeRad