Create qcom-preflight-checks.yml

[Sandhya1236]

Introduced QC Preflight Checks Workflow

Introduced the QC Preflight Checks GitHub Actions workflow with the following updates and configurations:

Added the QC Preflight Checks workflow
Configured the workflow trigger to use pull_request instead of pull_request_target
(Security improvement: pull_request_target runs with write permissions and access to secrets, which is unsafe for untrusted PRs)
Integrated the v2 version of the reusable workflow (qcom-reusable-workflow)
Defined a single job named preflight
Added job display name: Run QC Preflight Checks

Adopted the new v2 input parameter format:
enable-semgrep-scan
enable-dependency-review
enable-repolinter-check
enable-copyright-license-check
enable-commit-email-check
enable-commit-msg-check
enable-armor-checkers

Removed SEMGREP_APP_TOKEN secret, as it is no longer required in v2

Enabled Checks

Only the following checks are enabled:
enable-repolinter-check: true
enable-commit-email-check: true

All other checks are explicitly disabled.
For more details, refer to the https://github.com/qualcomm/qcom-reusable-workflows

[b49020]

@Sandhya1236 this TF-A repo is fork of upstream TF-A repo which exists here: https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/. So the pre-flight checks shouldn't be needed on this fork.

[mynameistechno]

@Sandhya1236 this TF-A repo is fork of upstream TF-A repo which exists here: https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/. So the pre-flight checks shouldn't be needed on this fork.

Yep @Sandhya1236 we should skip for forks, I guess it's not immediately clear this is a fork via the UI since it's missing the GitHub fork link.