Scan commit messages for Jira keys when syncing builds

What does this MR do and why?

As per #352411 (comment 1271002431) and #352411 (comment 1270669264), we are including pipeline.git_commit_message into the scanning Jira issue keys logic. This allows us to have all builds synced to Jira.

How to set up and validate locally

note prerequisite: gitlab-runner and JiraConnect

1. Checkout this branch
2. Create a first commit with a commit message in a new branch (branch_A)
3. Merge the branch_A into the branch_B
4. Merge the branch_B into the branch_C
5. The last deployment should be available in JIRA

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.

Related to #390888 (closed)