Aider-inspired polyglot benchmarks

[cte]

Description

Explainer video: https://www.youtube.com/watch?v=iidPH5KsNog
Exercises + web-ui: https://github.com/cte/Roo-Code-Benchmark
Inspiration: https://aider.chat/2024/12/21/polyglot.html#the-polyglot-benchmark

Additional context

Related Issues

Reviewers

---

Important

Introduces Aider-inspired polyglot benchmarks with Docker setup, CLI, and environment configuration, supporting multiple programming languages.

• Benchmark System:
  • Introduces Aider-inspired polyglot benchmarks supporting C++, Go, Java, JavaScript, Python, and Rust.
  • Adds benchmark directory with setup scripts, prompts, and configuration files.
  • Implements CLI in benchmark/src/cli.ts for running benchmarks.
• Docker and Environment:
  • Adds Dockerfile and .dockerignore for setting up a Docker environment.
  • Includes .env.local.sample for environment variable configuration.
• Scripts and Configuration:
  • Adds package.json in benchmark for managing dependencies and scripts.
  • Updates root package.json to include benchmark-related scripts.
  • Modifies knip.json and .vscodeignore to include benchmark paths.
• API and Core Changes:
  • Updates src/core/Cline.ts and src/exports/api.ts to handle new benchmark tasks.
  • Adds token usage tracking in src/exports/roo-code.d.ts and src/shared/getApiMetrics.ts.

^{This description was created by for f108dfa. It will automatically update as commits are pushed.}

[changeset-bot]

🦋 Changeset detected

Latest commit: e2bdce0

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
roo-cline	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[ellipsis-dev]

This pull request is quite large, with 27 files changed and over 3000 lines added. It includes a variety of changes such as new features, documentation updates, and refactoring across different areas like Dockerfiles, environment variables, CLI scripts, and coding exercise instructions.

To improve the review process and maintainability, it might be beneficial to split this pull request into smaller, more focused ones. Here are some suggestions on how the changes could be grouped:

1. Environment Setup and Configuration: This could include changes related to Dockerfiles, environment variables, and any setup scripts.
2. Documentation: All changes related to documentation, such as README updates and coding exercise instructions, could be grouped together.
3. CLI and Automation Scripts: Changes related to CLI scripts and automation tasks could form another pull request.
4. Refactoring and Code Improvements: Any refactoring or code improvements that are not directly related to new features could be separated.

Please consider splitting the pull request accordingly to facilitate a more efficient review process. Thank you!

[KJ7LNW]

neat! see also: #532 #1614