chore: Update build system dependencies

[cauliyang]

No description provided.

[sweep-ai]

Apply Sweep Rules to your PR?

• Apply: Leftover TODOs in the code should be handled.
• Apply: All new business logic should have corresponding unit tests in the tests/ directory.
• Apply: Any clearly inefficient or repeated code should be optimized or refactored.

[github-actions]

PR Analysis

• 🎯 Main theme: Updating build system dependencies
• 📝 PR summary: This PR updates the dependencies required by the build system in the pyproject.toml file. The 'wheel' package has been added to the list of required packages.
• 📌 Type of PR: Enhancement
• 🧪 Relevant tests added: No
• ⏱️ Estimated effort to review [1-5]: 1, because the PR is small and straightforward, only adding a single dependency to the build system.
• 🔒 Security concerns: No security concerns found

PR Feedback

• 💡 General suggestions: The PR is straightforward and doesn't seem to introduce any issues. However, it would be beneficial to include a description in the PR explaining why the 'wheel' package was added as a dependency.

• 🤖 Code feedback:

  • relevant file: pyproject.toml
    suggestion: Ensure that the 'wheel' package is compatible with the other dependencies and the overall project. [important]
    relevant line: "wheel",

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 [--extended]: Suggest improvements to the code in the PR. Extended mode employs several calls, and provides a more thorough feedback.
/ask <QUESTION>: Pose a question about the PR.
/update_changelog: Update the changelog based on the PR's contents.

To edit any configuration parameter from configuration.toml, add --config_path=new_value
For example: /review --pr_reviewer.extra_instructions="focus on the file: ..."
To list the possible configuration parameters, use the /config command.