Add benchmark workflow to save artifacts on main branch pushes

[Copilot]

This PR adds a new GitHub Actions workflow that automatically runs benchmarks and saves the results as artifacts whenever a PR is merged to the main branch.

Changes Made

• Created .github/workflows/benchmark.yml that:
  • Triggers on push to main branch (when PRs merge)
  • Sets up Java 23 and Gradle 8.14.2 (matching existing build workflow)
  • Runs ./gradlew :benchmark:run to generate benchmark results
  • Uploads the generated files as artifacts with 30-day retention:
    • benchmark/benchmark_results_*.csv
    • benchmark/benchmark_summary_*.txt

Workflow Details

The workflow uses glob patterns to handle timestamped filenames that are automatically generated by the benchmark system. For example:

• benchmark_results_2025-06-09_04-56-41.csv
• benchmark_summary_2025-06-09_04-56-41.txt

This ensures that performance tracking data is preserved and accessible for analysis across different commits to the main branch.

Fixes #17.

Warning

Firewall rules blocked me from connecting to one or more addresses

I tried to connect to the following addresses, but was blocked by firewall rules:

• esm.ubuntu.com
  • Triggering command: /usr/lib/apt/methods/https (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to my firewall allow list

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[Copilot]

Pull Request Overview

This PR introduces a new GitHub Actions workflow for running benchmarks and archiving the resulting artifacts on pushes to the main branch.

• Adds a new workflow file (.github/workflows/benchmark.yml) triggered on main branch pushes
• Sets up Java 23 and Gradle 8.14.2 for the benchmark job
• Runs the benchmark and uploads generated artifacts with a 30-day retention policy

[Copilot]

The PR description indicates that the benchmark should be run using './gradlew :benchmark:run'. Using 'gradle :benchmark:run' might bypass the project's local Gradle wrapper, leading to version discrepancies or configuration issues. Consider updating the command if the local wrapper is intended for use.

Suggested change

	run: gradle :benchmark:run
	run: ./gradlew :benchmark:run

[hossain-khan]

Nope! it's for a reason! gradlew on ci doesn't work for some reason.

[hossain-khan]