[Security Rules] Update security rules package to v8.7.3-beta.0

[terrancedejesus]

What does this PR do?

Update the Security Rules package to version 8.7.3-beta.0.
Autogenerated from commit https://github.com/elastic/detection-rules/tree/fc162529d9068dcadf6bcb5f5836aa8a1b764f79

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• If I'm introducing a new feature, I have modified the Kibana version constraint in my package's manifest.yml file to point to the latest Elastic stack release (e.g. ^7.13.0).

Author's Checklist

• Install the most recently release security rules in the Detection Engine
• Install the package
• Confirm the update is available in Kibana. Click "Update X rules" or "Install X rules"
• Look at the changes made after the install and confirm they are consistent

How to test this PR locally

• Perform the above checklist, and use package-storage to build EPR from source

Related issues

• [FR] Generate Historical Rule Files in Build Release Packages detection-rules#2715
• [FR] Generate initial historical package detection-rules#2688

Screenshots

None

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-04-20T02:56:31.656+0000

• Duration: 13 min 43 sec

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[terrancedejesus]

Package appears to pass all checks. All rule files have the version as _VERSION.json appended to it. Inside of each file, the id key's value is RULEID_VERSION. 11ea6bec-ebde-4d71-a8e9-784948f8e3e9 is a rule with a previous version in the v8.7.2 package.

Once merged, this will be pushed to EPR as a prerelease package and can be installed via Fleet for testing.

@xcrzx @banderror below are the Rule IDs that have historical rules with them:

11ea6bec-ebde-4d71-a8e9-784948f8e3e9
66883649-f908-4a5b-a1e0-54090a1d3a32
f33e68a4-bd19-11ed-b02f-f661ea17fbcc

[Mikaayenson]

LGTM

[elasticmachine]

Package security_detection_engine - 8.7.3-beta.0 containing this change is available at https://epr.elastic.co/search?package=security_detection_engine