feat(apps/prod/tekton/configs/triggers): parse profile param from cloud event extension

[wuhuizuo]

This pull request includes changes to the Tekton trigger configurations to improve the handling of the profile parameter. The main updates involve reading the profile parameter from the header or defaulting to 'release' and ensuring that the profile parameter is correctly passed to the bindings.

Key changes:

• apps/prod/tekton/configs/triggers/triggers/_/fake-github/fake-github-branch-push.yaml: Updated the custom-params to include the profile parameter from the header or default to 'release', and modified the binding to use $(extensions.custom-params.profile) for the profile parameter.
• apps/prod/tekton/configs/triggers/triggers/_/fake-github/fake-github-pr.yaml: Similar update to include the profile parameter in custom-params and use $(extensions.custom-params.profile) in the binding.
• apps/prod/tekton/configs/triggers/triggers/_/fake-github/fake-github-tag-create.yaml: Included the profile parameter in custom-params and updated the binding to use $(extensions.custom-params.profile).

[ti-chi-bot]

I have already done a preliminary review for you, and I hope to help you do a better job.

Summary of changes:
This pull request makes changes to the Tekton trigger configurations to improve the handling of the profile parameter. The changes involve reading the profile parameter from the header or defaulting to 'release' and ensuring that the profile parameter is correctly passed to the bindings.

Potential problems:
It is not clear from the pull request description whether the changes have been tested or not. It is important to ensure that changes have been tested before merging into the main branch.

Fixing suggestions:
To ensure that changes have been tested, the reviewer should ask the pull request author to describe the testing process or to provide evidence of successful testing. The reviewer could also suggest that the author adds testing instructions to the pull request description. Additionally, the reviewer should check that the changes comply with the project's coding standards and best practices.

[wuhuizuo]

/approve

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: wuhuizuo

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• apps/prod/OWNERS [wuhuizuo]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment