Add GitHub workflow to quiz Khoj on specified evals

[debanjum]

• Evaluate khoj on random 200 questions from each of google frames and openai simpleqa benchmarks across general, default and research modes
• Run eval with Gemini 1.5 Flash as test giver and Gemini 1.5 Pro as test evaluator models
• Trigger eval workflow on release or manually
• Make dataset, khoj mode and sample size configurable when triggered via manual workflow
• Enable Web search, webpage read tools during evaluation

[gitguardian[bot]]

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

| GitGuardian id | GitGuardian status | Secret | Commit | Filename | | | -------------- | ------------------ | ------------------------------ | ---------------- | --------------- | -------------------- | | [10005301](https://dashboard.gitguardian.com/workspace/453364/incidents/10005301?occurrence=170817591) | Triggered | Generic Password | 49199c0dc3a04a3bb322190d03348620d89a8d17 | .github/workflows/run_evals.yml | [View secret](https://github.com/khoj-ai/khoj/commit/49199c0dc3a04a3bb322190d03348620d89a8d17#diff-d93760297dc3e221894a21c9034ad77a3c8dffd2c9918613c90bd6d83fb84c16R46) | | [10005301](https://dashboard.gitguardian.com/workspace/453364/incidents/10005301?occurrence=170817592) | Triggered | Generic Password | 49199c0dc3a04a3bb322190d03348620d89a8d17 | .github/workflows/run_evals.yml | [View secret](https://github.com/khoj-ai/khoj/commit/49199c0dc3a04a3bb322190d03348620d89a8d17#diff-d93760297dc3e221894a21c9034ad77a3c8dffd2c9918613c90bd6d83fb84c16R94) |

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code. 2. Replace and store your secrets safely. [Learn here](https://blog.gitguardian.com/secrets-api-management?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) the best practices. 3. Revoke and [rotate these secrets](https://docs.gitguardian.com/secrets-detection/secrets-detection-engine/detectors/generics/generic_password#revoke-the-secret?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 4. If possible, [rewrite git history](https://blog.gitguardian.com/rewriting-git-history-cheatsheet?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data. To avoid such incidents in the future consider - following these [best practices](https://blog.gitguardian.com/secrets-api-management/?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) for managing and storing secrets including API keys and other credentials - install [secret detection on pre-commit](https://docs.gitguardian.com/ggshield-docs/integrations/git-hooks/pre-commit?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}