[Security][Detection rules] Pull in rule updates from v0.13.1 update

[rw-access]

Summary

Closes #102146

As of #101846, the rules were updated for 7.x and master to match the the Fleet package "Prebuilt Security Detection Rules" @ v0.13.1 (release notes). In that update, we fixed the ML jobs to use underscores instead of hyphens.

This pulls in that same rule update. Should be 41 updated rules and 4 new rules.

[elasticmachine]

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

[brokensound77]

LGTM

[spong]

This pulls in that same rule update. Should be 41 updated rules and 4 new rules.

Seeing Files changed 281 for this PR, looks like most of these extras are additional newlines being added to the query (without a version bump). Was there a change in the build pipeline that resulted in this, I don't think we need newlines at the end, no?

[kibanamachine]

💛 Build succeeded, but was flaky

• continuous-integration/kibana-ci/pull-request

• Commit: 7dbba29

• Storybooks Preview

• Flaky suites:

  • xpack-securitySolutionCypressChrome

---

Test Failures

Kibana Pipeline / general / "before all" hook for "should contain notes".Timeline notes tab "before all" hook for "should contain notes"

Link to Jenkins

Stack Trace

Failed Tests Reporter:
  - Test has not failed recently on tracked branches

AssertionError: Timed out retrying after 60000ms: Expected to find element: `.euiBadge`, but never found it.

Because this error occurred during a `before all` hook we are skipping the remaining tests in the current suite: `Timeline notes tab`

Although you have test retries enabled, we do not retry tests when `before all` or `after all` hooks fail
    at Context.eval (http://localhost:6121/__cypress/tests?p=cypress/integration/timelines/notes_tab.spec.ts:15943:14)

---

Metrics [docs]

✅ unchanged

History

• 💔 Build #135184 failed a8897ab

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[spong]

Configured a 7.13.2 install with all prepackaged rules installed, then checked out locally and verified rule updates were presented (41 in this instance), successfully installed, and that the ML Rules have been updated as well. LGTM! Thanks @rw-access! 🙂

Before:

After:

ML Job Fixed: