Update pipedv1 trigger to support adding trace commit hash to deployment model

[khanhtc1202]

What this PR does:

as title

Why we need it:

We must pass this value to the deployment model to use the Deployment Trace feature. This change is the same as we did in pipedv0 logic (ref: pipedv0/trigger/deployment)

Which issue(s) this PR fixes:

Follow #5625

Does this PR introduce a user-facing change?:

• How are users affected by this change:
• Is this breaking change:
• How to migrate (if breaking change):

[Warashi]

LGTM

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 2 lines in your changes missing coverage. Please review.

Project coverage is 25.57%. Comparing base (bc1a61b) to head (ecd6776).
Report is 7 commits behind head on master.

Files with missing lines	Patch %	Lines
pkg/app/pipedv1/trigger/deployment.go	0.00%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #5649      +/-   ##
==========================================
+ Coverage   25.54%   25.57%   +0.02%     
==========================================
  Files         477      477              
  Lines       50945    51074     +129     
==========================================
+ Hits        13016    13060      +44     
- Misses      36924    37009      +85     
  Partials     1005     1005              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.