chore: update dependencies, compiler settings, and config files

[shuhuiluo]

Removed unused imports in Rust and Solidity files, upgraded Solidity compiler version to 0.8.28, and adjusted Foundry and Hardhat configs. Incremented package version to 0.10.0 and upgraded Alloy dependency to version 0.9.

Summary by CodeRabbit

• Version Update

  • Package version bumped from 0.9.0 to 0.10.0
  • Updated alloy crate dependency from version 0.8 to 0.9

• Configuration Changes

  • Modified Solidity compiler version to 0.8.28
  • Disabled via-ir compilation option
  • Removed BNB Smart Chain RPC endpoint

• Code Refactoring

  • Updated error handling in Rust modules
  • Removed specific import statements in contracts and source files

[coderabbitai]

Walkthrough

Bazinga! The pull request introduces a series of version updates and configuration modifications across multiple files. The primary changes involve updating the Solidity compiler version to 0.8.28, modifying the alloy crate version to 0.9, and adjusting compilation settings from via-ir = true to via-ir = false. Additionally, some import statements have been removed, and error handling mechanisms have been slightly refined.

Changes

File	Change Summary
Cargo.toml	- Package version bumped to 0.10.0 - alloy dependency updated to version 0.9
contracts/PositionUtils.sol	- Removed imports for PoolAddress and PoolAddressPancakeSwapV3
foundry.toml	- Added Solidity compiler version 0.8.28 - Changed via-ir to false - Removed bnb_smart_chain RPC endpoint
hardhat.config.ts	- Updated Solidity version to 0.8.28 - Changed viaIR to false
src/pool_lens.rs	- Removed anyhow::Result import - Updated return types to use module-specific Error
src/position_lens.rs	- Removed anyhow::Result import - Updated return types to use module-specific Error

Poem

Versions dance, configs shift and sway,
Compiler's whispers guide the code's ballet
Imports vanish, errors refine their art
In this digital realm, precision plays its part! 🧩
Bazinga! Code evolution's sweet embrace 🚀

Tip

CodeRabbit's docstrings feature is now available as part of our Early Access Program! Simply use the command @coderabbitai generate docstrings to have CodeRabbit automatically generate docstrings for your pull request. We would love to hear your feedback on Discord.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between dbdd44e and bd764c6.

📒 Files selected for processing (6)

• Cargo.toml (2 hunks)
• contracts/PositionUtils.sol (0 hunks)
• foundry.toml (1 hunks)
• hardhat.config.ts (1 hunks)
• src/pool_lens.rs (0 hunks)
• src/position_lens.rs (0 hunks)

💤 Files with no reviewable changes (3)

• contracts/PositionUtils.sol
• src/position_lens.rs
• src/pool_lens.rs

🔇 Additional comments (6)

hardhat.config.ts (2)

12-12: Fascinating upgrade.
You have updated the Solidity compiler version to 0.8.28. Keeping pace with improvements is commendable.

---

18-18: 🧹 Nitpick (assertive)

Just a reminder, dear friends.
Disabling viaIR could reduce compile times but might limit some advanced optimizations. Confirm that this meets all performance requirements.

foundry.toml (1)

8-8: Version consolidation achieved.
Excellent job aligning the Solidity compiler version with Hardhat.

Cargo.toml (3)

3-3: Significant version bump.
Advancing the package to 0.10.0 signals a new iteration. Verify any referencing code is updated accordingly.

---

23-23: Consistency, my dear colleagues.
Ensuring the dev dependency matches the primary dependency is an admirable display of uniformity.

---

15-15: 🧹 Nitpick (assertive)

Alloy rises!
Upgrading alloy to 0.9 can unlock fresh features. Verify compatibility with existing logic to avoid any meltdown.