Edit max_signals field for custom rules in UI [classic]

[joepeeples]

Important

Do not merge to main until after 8.14.0 release, maybe until 8.15 feature freeze. This is to avoid adding 8.15 features into previous versions' branches (since those branches would be cut from main).

Contributes to #5029.

Preview

• Create a detection rule | Configure advanced rule settings (optional)
  
• Alert suppression
• Create rule API
• Update rule API

Twin PR for serverless

• https://github.com/elastic/staging-serverless-security-docs/pull/328

[github-actions]

A documentation preview will be available soon.

• 🔨 Buildkite builds
• 📚 HTML diff
• 📙 Preview page

Request a new doc build by commenting

• Rebuild this PR: run docs-build
• Rebuild this PR and all Elastic docs: run docs-build rebuild

_{run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.}

_{If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.}

[approksiu]

Suggested some changes in a comment

[dplumlee]

This lines up correctly with the logic we have implemented, thanks @joepeeples!

[banderror]

Looks awesome! 👍

[benironside]

LGTM

[mergify]

This pull request is now in conflicts. Could you fix it @joepeeples? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b 5029-max_signals-editable-classic upstream/5029-max_signals-editable-classic
git merge upstream/main
git push upstream 5029-max_signals-editable-classic