[AI4DSOC] Change rules details page capabilities

[tomsonpl]

This approach was suggested by @semd , big thank you 👍

Summary

This PR enhances the navigation and access control for the Security Solution's rules management functionality.
It introduces a dedicated rulesManagement page name in the deep links system and updates the routing configuration to properly handle rule details pages while restricting access to editing capabilities and the landing page based on user permissions.
It's a follow up to this PR: #219111

Changes

• Rule details pages are now accessible in AI SOC
• Rule editing functionality is restricted in AI SOC (security, but not ai_soc)
• Rules landing page access is accessible in AI SOC (doesn't hurt us since it's anyway not accessible through UI in serverless)
• Rules management is restricted in AI SOC
• Removed render overwrite to enable rule details links
• Added test coverage for the new routing behavior

Testing

• Updated Cypress tests to verify the correct routing behavior
• Tested with different user roles to ensure proper access control
• Verified that rule details pages open correctly while edit functionality is appropriately restricted

[tomsonpl]

/ci

[vgomez-el]

LGTM!

[rylnd]

No logic was changed in Detection Engine code; only the addition of a few constants.

I think @elastic/security-detection-rule-management should confirm whether these capabilities are correct; besides that, this LGTM.

[xcrzx]

Tested the navigation locally in both AI4SOC and Complete tiers. The rule details page is accessible as expected, and no regressions spotted in the Complete tier. LGTM 👍

[stephmilovic]

Code review only, LGTM!!

[PhilippeOberti]

Blocking the merge as allowing access to the rule details page in AI4DSOC might not be the right move right now.
As you can see in the video below, we have buttons which lead to pages not found (like the edit button), we have actions available that probably should not be (duplicate, delete...), we have the chart that has cell actions, we have the wrong table, access to all the non-AI4DSOC flyouts…

[PhilippeOberti]

So @jamesspi decided to go ahead and allow the page to be visible, despite all the UI inconsistencies and issues.

I'm then approving the PR. I will start working on cleaning up the UI for AI4DSOC, starting with the alerts table.

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 00ac76c

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
securitySolution	9.1MB	9.1MB	+450.0B

Page load bundle

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

id	before	after	diff
securitySolution	91.0KB	91.0KB	+70.0B
securitySolutionEss	33.7KB	33.7KB	+37.0B
securitySolutionServerless	52.3KB	52.3KB	+37.0B
total			+144.0B

cc @tomsonpl

[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 219260 locally
cc: @tomsonpl

[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 219260 locally
cc: @tomsonpl

[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 219260 locally
cc: @tomsonpl

[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 219260 locally
cc: @tomsonpl