[Security Solution] Refactor forms logic on Rule Creation, Edit and Details pages, and overlap with Bulk Actions

[spong]

Creating this issue as an outcome of working #149885 and complexities in tracking down the root cause of stale events in the Edit Rule Actions flow as detailed in #142217.

It's been some time (~3 years) since the Rule Creation/Edit flows (and subsequently Rule Details as it's a read-only representation of the former) were created, and since then there have been continuous updates and enhancements to the underlying ES UI: Form lib (internal docs). This tech debt issue is for revisiting our architecture between these pages/flows, and refactoring to have a better integration between the form lib, the trigger_actions_ui components used for actions, and the different security components used here and within the Bulk Actions flyout.

For additional context, please see the following issues/PR's:

• [Security Solution][Detections] fixes validation issues in rules actions form #141811 (comment)
• [Security Solution] Validation is not triggered correctly in rule actions form #142217
• [Security Solution] Editing the Action Message of a detection rule results in cursor jumping to end  #149885
• [Security Solution] Fix cursor jumping to end of text area when editing Rule Action Message #150823

And note that as per the form libs docs:

Unless your parent component needs to be aware of every field value change in the form (which should rarely be needed), you don't want to use the useFormData() hook and forward the data from there. This would create unnecessary re-renders. Instead it is better to forward the getFormData() handler on the form.

Please see these references of useFormData in the about, define, schedule, and actions steps.

Additionally, there are a few inconsistencies in how we manage errors between the Bulk Actions flyout UI and the Edit Rule UI. Currently the Edit Rule UI will validate the whole action on connector selection and display the error callout immediately (instead of waiting for form submission or loss of focus from the new fields just added), and the Bulk Actions UI does the opposite and doesn't always show the error and will fall back to showing an error toast from the failed http request (not always validating on submit, depends on form state).

[elasticmachine]

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

[elasticmachine]

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