feat : improve controller trigger log

[sienna011022]

Summary

Improve trigger log readability by providing more contextual information.

Problem

When debugging alerts, it is difficult to determine whether a trigger was actually fired.
In particular, the meaning of randomHashKey is unclear, making it hard to identify which revision caused the trigger.

"Trigger on-deployedresult: [{[0].randomHashKey  [app-deployed] false}]"

Solution

Improve the trigger log message to explicitly include revision and template information.

Trigger 'my-trigger' TRIGGERED | revision: abc123 | templates: [template1]

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 59.98%. Comparing base (da04400) to head (9280e39).
⚠️ Report is 13 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #417      +/-   ##
==========================================
+ Coverage   55.41%   59.98%   +4.57%     
==========================================
  Files          46       47       +1     
  Lines        4125     3619     -506     
==========================================
- Hits         2286     2171     -115     
+ Misses       1511     1102     -409     
- Partials      328      346      +18     

☔ 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.