[Alerting v2] Remove condition field

[benakansara]

Resolves https://github.com/elastic/rna-program/issues/274

Summary

• Removes the "Trigger condition" (WHERE clause) field from the evaluation section of the rule create/edit form
• Removes the recovery condition field
• Removes alert condition block from rule details page
• Updates preview hook to use only evaluation.query.base / recoveryPolicy.query.base, ignoring the condition field
• Removes condition from API payloads on write and ignores it from API responses on read, guarding against stale values from API-created rules

Edit rule - evaluation

Edit rule - recovery

Rule details page

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR removes the condition field feature from the Alerting v2 rule form, fundamentally changing how evaluation and recovery queries are processed. While the author owns all changed files, removing feature functionality represents a significant runtime behavior change that warrants human review to confirm the removal aligns with product intent.

^{You can customize Macroscope's approvability policy. Learn more.}

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 0d6a32e

Failed CI Steps

• FTR Configs #211

Test Failures

• [job] [logs] FTR Configs #211 / serverless search UI Rule details Edit rule with deleted connector should show and update deleted connectors when there are existing connectors of the same type

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
alertingVTwo	445	440	-5

Async chunks

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

id	before	after	diff
alertingVTwo	280.7KB	269.2KB	-11.5KB

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
alertingVTwo	148.1KB	147.7KB	-385.0B

History

• 💔 Build #421362 failed afe9b4f

cc @benakansara