Fix: automated benchmark testing via Job Summary

[yinjie-z]

💡 Issue Reference

Issue: #217

💻 What does this address?

I found that pull_request_target triggers often only take full effect once the workflow is merged into the repository's default branch (main). Otherwise, using a bot to post comments on PRs from forks frequently hits permission blocks (403 Forbidden).

Here's the doc :

This event runs in the context of the default branch of the base repository, rather than in the context of the merge commit, as the pull_request event does.

📟 Implementation Details

• Uses GITHUB_STEP_SUMMARY to display performance data.
• Bypasses the 403 Forbidden issues typically found when bots try to comment on PRs from forks.
• Provides a clean table showing Execution Time and Memory Growth.

[yinjie-z]

To see the table results :

1. Go to the Checks tab of this PR.
2. Click on Benchmark Test in the sidebar.
3. Select Summary to view the performance table (Avg Time & Memory Growth).

OR

1. Scroll down to the Checks area at the bottom of the PR.
2. Click View Details next to Benchmark Test job
3. Select Summary in the sidebar to view the table

Example in Job Summary