Archive Attack Coverage Update Workflow

[shashank-elastic]

Pull Request

Issue link(s): Part of Release Automation Maintenance - refer

Summary - What I changed

• We have ran the combined workflow to update Attack coverage along with log versions here
• The new PR now contains Attack coverage updation as well as version lock changes - Lock versions for releases: 8.14,8.15,8.16,8.17,8.18,9.0 #4820
• The individual workflow for updating coverage can be archived.

How To Test

Checklist

• Added a label for the type of pr: bug, enhancement, schema, maintenance, Rule: New, Rule: Deprecation, Rule: Tuning, Hunt: New, or Hunt: Tuning so guidelines can be generated
• Added the meta:rapid-merge label if planning to merge within 24 hours
• Secret and sensitive material has been managed correctly
• Automated testing was updated or added to match the most common scenarios
• Documentation and comments were added for features that require explanation

Contributor checklist

• Have you signed the contributor license agreement?
• Have you followed the contributor guidelines?