Create an Issue in Kibana for MITRE Updates

[shashank-elastic]

Issues

#3100

Summary

• Most of the code logic was originally pinned in the issue.
• We need to check the GitHub token and its permission to create issue in kibana repository
• We have moved to use market place changed files to fetch filename as opposed to git diff originally ideated.
• We have added an activity type for pull_request : [opened].
  • If no activity types are specified, the workflow runs when a pull request is opened or reopened or when the head branch of the pull request is updated, creating duplicate issues in kibana which is not required.
  • The workflow will run only when the PR is opened at the first time.

Testing

• Sample Run by introducing file path change - https://github.com/elastic/detection-rules/actions/runs/9749396691/job/26906449473?pr=3796
• Issue created in detection-rules as opposed to kibana [ to not pollute an external repository] Update MITRE ATT&CK to v15.1.1. #3859

[Mikaayenson]

I can't tell how this was tested. Do you have screenshots or any evidence that this works?

[eric-forte-elastic]

🟢 Manual review, looks good to me! 👍