[Security Solution][Detections] Adds SOM privilege check for Related Integrations

[spong]

Summary

If SOM privileges are None the Related Integrations feature incorrectly shows all integrations as Not Installed even if some of them may be. This PR adds a client-side privilege check and falls back to the basic UI that just shows the integration name+link and not any install information.

Test instructions:

To test, configure a role with SOM privileges as None, e.g.

Then UI should fall back to no installed information:

Rule Details:

Rule Management:

TODO:

• A test to exercise this fallback (either unit or cypress w/ specific role should do)
• Ensure docs mention the required privileges for this feature

Checklist

Delete any items that are not applicable to this PR.

• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios

[elasticmachine]

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

[kibana-ci]

💔 Build Failed

• Buildkite Build
• Commit: 65f3cac
• Interpreting CI Failures
• Storybooks Preview
• Webpack Bundle Analyzer

Failed CI Steps

• Jest Tests #1

Test Failures

• [job] [logs] Jest Tests #1 / IntegrationDescription Shows total events returned

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	5.2MB	5.2MB	+165.0B

History

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

cc @spong

[elasticmachine]

Pinging @elastic/security-detections-response (Team:Detections and Resp)

[spong]

Closing in favor of #134299