[Security Solution] Rule creation/editing forms improvements

[maximpn]

Summary

Rule creation and editing forms implementation contain multiple suboptimal logic which might be improved. It became prominent while working on UI for Prebuilt Rule Customization workflow in https://github.com/elastic/kibana/issues/171520. These share the same rule fields editing components. Due to time constraints managed technical debt was introduced and additionally it wasn't possible to address existing technical debt. This ticket contains rule creation and editing forms related technical debt.

Tasks

• [ ] Reintegrate DataSourceEdit component to creation/editing forms
• [ ] Refactor EQL query bar to get rid of unnecessary data view creation
• [ ] Alert Suppression shouldn't be valid if there is no matching fields. The same issue is in Prebuilt Rule Customization UI https://github.com/user-attachments/assets/7081ad69-5c19-40e9-88a7-735bb777f6b3
• [ ] Address complexity of getFlattenedArrayFieldNames() in Required fields. Ideally we should have self describing code explaining why we need flattened array fields. Refactoring for better readability would be great. Additionally we should have unit tests to cover this functionality, see https://github.com/elastic/kibana/pull/196642#discussion_r1836559759.

...

TBD

[elasticmachine]

Pinging @elastic/security-detection-engine (Team:Detection Engine)

[elasticmachine]

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

[elasticmachine]

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