Remove mock reports

[waynehamadi]

Background

Changes

PR Quality Checklist

• I have run the following commands against my code to ensure it passes our linters:

  black . --exclude test.py
  isort .
  mypy .
  autoflake --remove-all-unused-imports --recursive --ignore-init-module-imports --ignore-pass-after-docstring --in-place agbenchmark

[github-actions]

PR Analysis

• 🎯 Main theme: Removal of mock reports and modification of CI workflow
• 📌 Type of PR: Refactoring
• 🧪 Relevant tests added: No
• ✨ Focused PR: Yes, the PR is focused as it clearly states in the title and description that it is about removing mock reports. All changes in the PR are related to this task.
• 🔒 Security concerns: No, the PR does not introduce any obvious security concerns as it mainly involves the removal of mock reports and a minor change in the CI workflow.

PR Feedback

• 💡 General PR suggestions: The PR is well-structured and follows good practices. It would be beneficial to include a brief explanation in the PR description about why these specific mock reports are being removed and how it impacts the project. Additionally, the change in the CI workflow condition could be explained more clearly.

How to use

To invoke the PR-Agent, add a comment using one of the following commands:
/review [-i]: Request a review of your Pull Request. For an incremental review, which only considers changes since the last review, include the '-i' option.
/describe: Modify the PR title and description based on the contents of the PR.
/improve: Suggest improvements to the code in the PR.
/ask <QUESTION>: Pose a question about the PR.

To edit any configuration parameter from 'configuration.toml', add --config_path=new_value
For example: /review --pr_reviewer.extra_instructions="focus on the file: ..."