[Docs][Exceptions] - Auto fill exceptions from alert data

[yctercero]

Description

This issue aims to enhance the feature of auto-populating Rule Exceptions that are created from Alerts.

Currently, Rule Exceptions can be created from both the Alerts table and the Alert summary flyout action button. The goal is to automatically populate the Rule Exceptions with the relevant fields extracted from the Alert. However, certain fields that are deemed irrelevant to the Rule Exception need to be stripped out as described here.

Version: This feature should be in 8.9
PR: elastic/kibana#159029

Doc updates

• Add exceptions to a rule: Update steps 1 and 2 (screenshot in step 2 included)
• Add Elastic endpoint exceptions: Screenshot in step 1 and possibly text in step 2.

Notes

• Will also need to update the endpoint exception docs to show that conditions (fields and values) for endpoint exceptions are also auto-populated when users create a new exception from the More Actions menu or Alerts table.
  • The fix ([Security Solution] [Exceptions] Fix Exception Auto-populate from Alert actions kibana#159908) for this was only backported to 8.9/8.10 so will likely only need to update the 8.9 docs.
• Condition fields and values are only auto-populated when users create a new exception from an alert (Take action > Add rule exception) or from the Alert table (More Actions menu (…​) > select Add rule exception).
  • [Security Solution] [Exceptions] Fix Exception Auto-populate from Alert actions kibana#159908 adds functionality to the Take action menu.
  • Condition fields/values are not auto-populated when users add an exception to a rule from the Shared Exception Lists page.