[Security Solution] Add history_window_start and new_terms_fields editable fields

[nikitaindik]

Partially addresses: #171520

Summary

Changes in this PR:

• history_window_start and new_terms_fields are now editable in the Rule Upgrade flyout
• Extracted fields into separate components that are easier to reuse (NewTermsFieldsEdit and HistoryWindowStartEdit)

Testing

• Ensure the prebuiltRulesCustomizationEnabled feature flag is enabled.
• To simulate the availability of prebuilt rule upgrades, downgrade a currently installed prebuilt rule using the PATCH api/detection_engine/rules API.
  • Set version: 1 in the request body to downgrade it to version 1.
  • Modify other rule fields in the request body as needed to test the changes.

[elasticmachine]

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

[elasticmachine]

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

[elasticmachine]

Pinging @elastic/security-detection-rule-management (Team:Detection Rule Management)

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: a67e1b0
• Storybooks Preview

Failed CI Steps

• FTR Configs #57
• FTR Configs #87

Test Failures

• [job] [logs] FTR Configs #57 / Screenshots - serverless security UI response ops docs security cases security case settings case settings screenshot
• [job] [logs] FTR Configs #87 / Visualizations - Group 3 lens app - TSVB Open in Lens Table should convert color ranges

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
securitySolution	6202	6213	+11

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
securitySolution	13.4MB	13.4MB	+1.4KB

cc @nikitaindik