[Security AI Assistant] Update anonymization privileges

[YulNaumenko]

Added new sub-feature to AI-Assistant which allows to grant user role privilege to edit Anonymization fields:

How to test:

1. Create user role, which has access to Security and Actions/Connectors and AI Assistant.
2. Customize sub-feature privileges: Remove checkbox for Update anonymization fields.
3. Save role.
4. Create/update existing user with the new role.
5. Go to Security AI Assistant settings and open Anonymization tab.
6. For the user role with removed privilege to edit anonymization, all actionable buttons should be disabled. Button Save will remain enabled, because it correspond to all Assistant settings.
7. Public API "/api/elastic_assistant/anonymization_fields/_bulk_action" should return "Forbidden" 403 access error.

How it looks when no privilege for the user role:

@patrykkopycinski please adopt it after merging this PR to the new UX

[jamesspi]

@YulNaumenko @spong, I think this looks great. Perhaps the wording could be improved a bit to show that it's field selection and anonymization. Also, since this will also effect insights, we should probably update the main title (Elastic AI Assistant) to reflect that?

For the feature privilege itself -

Maybe the name/title would be:

"Field Selection and Anonymization"

Description:

"Change the default fields that are allowed to be used by the AI Assistant and AI Insights. Anonymize any of the content for the selected fields".

For the text next to the tick box, maybe: "Allow changes", unless we want to also go for the All/None selector instead

[stephmilovic]

Looks like the bulk actions still work. You get an error when you try to save, but we should disable any updates in the UI anyways.

Also, what do you think about adding a tool tip explaining why the toggles/bulk actions are disabled?

[YulNaumenko]

Looks like the bulk actions still work. You get an error when you try to save, but we should disable any updates in the UI anyways.

fixed in 7d3fd66

Also, what do you think about adding a tool tip explaining why the toggles/bulk actions are disabled?

For now, till the new design will be ready, I just removed toolbar, because no sense to have bulk actions and select

[stephmilovic]

LGTM, thanks for the fix!

[dplumlee]

Rule management changes LGTM

[elasticmachine]

Pinging @elastic/security-solution (Team: SecuritySolution)

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: eb5a8ef

Metrics [docs]

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id	before	after	diff
@kbn/elastic-assistant	131	132	+1

Async chunks

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

id	before	after	diff
securitySolution	17.2MB	17.2MB	+799.0B

Unknown metric groups

API count

id	before	after	diff
@kbn/elastic-assistant	153	154	+1

History

• 💔 Build #203411 failed 70ee82e
• 💔 Build #203391 failed 4096b50
• 💔 Build #203341 failed 1cd6da2

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

cc @semd @YulNaumenko