[Security Solution] Support rule type change during upgrade

[xcrzx]

Resolves: #180395

Summary

Supports rule type change when upgrading a rule to a newer version, covering scenarios where the current version's rule type differs from the target version. Regardless of the feature flag, the rule should be updated to the target version.

Behavior with Rule Customization OFF

No changes expected. A rule with a rule type change can be updated through:

• The single rule update option ✅
• The bulk update option ✅
• The Update All option ✅

Behavior with Rule Customization ON

Regardless of whether the rule has customizations:

• The rule cannot be updated using the single update option ❌
• The rule is excluded from bulk updates ❌
• The rule is excluded from Update All ❌
• The rule can only be updated after manually reviewing changes via the update flyout ✅

The update flyout includes a warning message, advising users to back up any customizations the rule may have. The flyout is in read-only mode:

[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: 54a3d70

Failed CI Steps

• FTR Configs #59

Test Failures

• [job] [logs] FTR Configs #59 / Screenshots - serverless security UI response ops docs security cases security case settings case settings screenshot

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
securitySolution	6202	6203	+1

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.0KB

History

• 💔 Build #251530 failed 7705690
• 💔 Build #251371 failed 1ce2460

cc @xcrzx