Remove graphql logs

[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 GraphQL logs
• 📌 Type of PR: Refactoring
• 🧪 Relevant tests added: No
• ✨ Focused PR: Yes, because the title and description clearly state that the purpose of the PR is to remove GraphQL logs, and the code changes align with this purpose.
• 🔒 Security concerns: No, because the changes in this PR are related to logging and do not introduce any new functionality or dependencies that could potentially lead to security vulnerabilities.

PR Feedback

• 💡 General PR suggestions: The PR is generally well-structured and follows good practices. However, it would be beneficial to add tests to ensure that the removal of logs does not affect the functionality of the application. Additionally, it would be helpful to provide more context in the PR description about why the logs are being removed and what impact this might have on debugging or monitoring.

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: ..."