Lock versions for releases: 7.16,8.0,8.1,8.2,8.3,8.4,8.5

[github-actions]

Lock versions for releases: 7.16,8.0,8.1,8.2,8.3,8.4,8.5.

• Autogenerated from job lock-versions: pr.

[terrancedejesus]

This is the second locked versions PR for the 8.5 release. Typically we lock once and work from that PR's merge commit to keep the detection rules is a static state as we release updates to Kibana and the pre-built rules integration package.

Why we locked again - After our initial lock and Kibana rule updates, we merged a PR to re-factor the related_integrations field value at build time to make it more resilient, add unit testing and address an expectation from the Kibana side for the version where we can add ^. During the merge, backporting failed at the 8.3 branch as a result of a version comparison bug in integrations.py, a separate PR was made and a solution provided for this. Since this ultimately adjusts ALL integration rules, they will be considered "dirty" during the package building and thus version will be bumped by 1.

To avoid version collisions and thus Kibana not understanding that updates are present during the next 8.6 release we needed to lock versions again. When checking the file adjustments, all rules that are "integration" rules will receive version bumps and are expected.

[terrancedejesus]

LGTM. The biggest check I wanted to ensure, based on the timing, was rule version and SHA256 diffs to integration rules, which seems to be the case.

Typical checks:

• No double/triple/etc. version bumps
• For each version bump, the SHA256 changed
• For new rules in 8.5, they went from 1-2 as expected if an integration rule

[Mikaayenson]

LGTM