Replace fail-on-alert with comment-on-alert on benchmark test

[XSAM]

Part of #4537

The fail-on-alert would fail the entire benchmark CI like this https://github.com/open-telemetry/opentelemetry-go/actions/runs/10235553562/job/28367685489. With this behavior, we are not able to cache the benchmark result, thus the next benchmark cannot find the previous result to compare. https://github.com/open-telemetry/opentelemetry-go/actions/runs/10250450573

This PR replaces fail-on-alert with comment-on-alert, so the benchmark of the next commit can always find the result from the previous commit even if the previous CI triggers an alert. And, we can still receive the alert by comment, like this benchmark-action/github-action-benchmark@077dde1#commitcomment-36047186.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 84.4%. Comparing base (127d068) to head (5248400).

Additional details and impacted files

@@          Coverage Diff          @@
##            main   #5671   +/-   ##
=====================================
  Coverage   84.4%   84.4%           
=====================================
  Files        272     272           
  Lines      22516   22516           
=====================================
+ Hits       19024   19025    +1     
+ Misses      3156    3155    -1     
  Partials     336     336           

see 1 file with indirect coverage changes

[pellared]

I think that we should use actions/cache/save and actions/cache/restore actions instead of a single actions/cache action.

This way we can still have the benchmark action failed and the cache being updated (we can run actions/cache/save even if the workflow is failed). Otherwise, if we do not fail the workflow, how we would know that something is wrong?

References:

• https://github.com/actions/cache/tree/main/restore
• https://github.com/actions/cache/blob/main/save

[XSAM]

Otherwise, if we do not fail the workflow, how we would know that something is wrong?

The comment-on-alert should also send a notification to the author of the commit. But, yeah, a failed CI is more clear than a notification. I created #5694 to replace this PR.