Add ability to benchmark pull requests

[rashidnhm]

Context: Add ability to benchmark a pull request

Description of the Change:
This pull request adds the ability to benchmark a PR.

When a user with either admin or maintain permissions comments /benchmark on a pull request, this workflow will trigger a webhook to benchmarks repo with sufficient details to benchmark the PR, it is then up to the benchmarks action to report back with results.

Once the webhook is sent, a 👍 reaction is added to the comment to indicate it was successful.

Benefits:
New feature.

Possible Drawbacks:
This is an MVP product, we may want to iterate on this to add further information or functionality. However, the current state is sufficient for the basic needs of benchmarking.

Related GitHub Issues:
None. sc-73314

[github-actions]

Hello. You may have forgotten to update the changelog!
Please edit doc/releases/changelog-dev.md with:

• A one-to-two sentence description of the change. You may include a small working example for new features.
• A link back to this PR.
• Your name (or GitHub username) in the contributors section.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.70%. Comparing base (f2e1e73) to head (019c0f9).
Report is 2 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #6274   +/-   ##
=======================================
  Coverage   99.70%   99.70%           
=======================================
  Files         444      444           
  Lines       42226    42226           
=======================================
  Hits        42103    42103           
  Misses        123      123           

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

[jay-selby]

LGTM. Thanks Rashid!

I think there is some future work on the benchmark side to cleanly format the output reported back to the PR.

[mudit2812]

Looks good to me, but is it possible to try it out before we merge? Just want to see it in action to verify it works. The code itself looks fine to me, but I also don't use javascript much. Or is it not possible since the PR on the benchmarks suite-side is still open?

[rashidnhm]

Looks good to me, but is it possible to try it out before we merge? Just want to see it in action to verify it works. The code itself looks fine to me, but I also don't use javascript much. Or is it not possible since the PR on the benchmarks suite-side is still open?

I have tried to get the code to work as much as I could in a private fork ... however, yes, none of the changes here can be tested as part PR unfortunately

[mudit2812]

Looks good to me, but is it possible to try it out before we merge? Just want to see it in action to verify it works. The code itself looks fine to me, but I also don't use javascript much. Or is it not possible since the PR on the benchmarks suite-side is still open?

I have tried to get the code to work as much as I could in a private fork ... however, yes, none of the changes here can be tested as part PR unfortunately

All good then. This is all pretty early iteration work anyway, we can always come back later with bug fixes 😄