[Security Solution] Users can't upgrade rules without customizations when rule type changed

[maximpn]

Summary

Users can't upgrade Elastic rules without customizations but with rule type change rule update preview flyout.

Steps to reproduce:

1. Setup the environment as described below
2. Open Okta User Sessions Started from Different Geolocations rule in rule update preview flyout
3. Notice Rule type change warning message
4. Try to upgrade the rule by clicking Update rule button in table row or by bulk upgrading

Expected behavior: The rule gets upgraded

Actual behavior: Rule is upgradable only from the rule update preview flyout

Screenshots (if relevant):

Setup the environment

• Ensure the prebuiltRulesCustomizationEnabled feature flag is enabled

• Allow internal APIs via adding server.restrictInternalApis: false to kibana.dev.yaml

• Clear Elasticsearch data

• Run Elasticsearch and Kibana locally (do not open Kibana in a web browser)

• Install an outdated version of the security_detection_engine Fleet package

  curl -X POST --user elastic:changeme  -H 'Content-Type: application/json' -H 'kbn-xsrf: 123' -H "elastic-api-version: 2023-10-31" -d '{"force":true}' http://localhost:5601/kbn/api/fleet/epm/packages/security_detection_engine/8.14.1

• Install prebuilt rules

  curl -X POST --user elastic:changeme  -H 'Content-Type: application/json' -H 'kbn-xsrf: 123' -H "elastic-api-version: 1" -d '{"mode":"ALL_RULES"}' http://localhost:5601/kbn/internal/detection_engine/prebuilt_rules/installation/_perform

[elasticmachine]

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

[elasticmachine]

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

[elasticmachine]

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

[banderror]

@maximpn I think this is expected, intentional behavior at this stage. It's not a high-impact bug.

When discussing with @approksiu and @xcrzx what would be the simplest and easiest to implement MVP solution, we came up with https://github.com/elastic/kibana/issues/180395. We should revisit and improve this UI as part of Milestone 4, here's a new ticket for that:

• https://github.com/elastic/kibana/issues/203145

I'm gonna close this one. Feel free to reopen if anyone disagrees.