fix(checker): add committer fields to dangerous workflow contex

[LoveChauhan-18]

What kind of change does this PR introduce?

Bug fix

• PR title follows the guidelines defined in our pull request documentation

What is the current behavior?

The dangerous workflow check (containsUntrustedContextPattern) does not flag committer.name and committer.email from GitHub webhooks as untrusted. These fields can be easily controlled by attackers.

What is the new behavior (if this is a feature change)?**

Added committer.email and committer.name for both the head_commit and commits.* objects directly into the untrusted context regex.

• Tests for the changes have been added (for bug fixes/features)

Which issue(s) this PR fixes

Fixes #4926

Special notes for your reviewer

Added the missing fields to the regex alongside the existing author checks and updated the dangerous_workflow_test.go fixture table with the corresponding cases.

Does this PR introduce a user-facing change?

No

NONE

[justaugustus]

@LoveChauhan-18 — While we are happy to consider contributions from new contributors, this is the second time you've opened a PR:

• without any kind of disclosure that you're submitting AI-assisted development contributions
• that has given the appearance that you have either:
  1. copied someone else's work without attribution
  2. appeared to not recognize work that was already opened for review in the repo: fix: detect committer name/email as untrusted input in Dangerous Workflow check #4968

I am closing this PR and issuing a warning: please do not do this again