feat: apply connect-v2 updates

[beer-1]

Summary by CodeRabbit

• Documentation

  • Updated compatibility table in the README to reflect new version numbers for L1 Node, MiniMove, MiniWasm, and MiniEVM.
  • Improved formatting in executor/README.md for better readability and clarity of configuration examples.

• Chores

  • Updated various dependencies in the go.mod file to their latest versions, ensuring improved stability and performance.
  • Streamlined configuration in GitHub workflows by removing unnecessary environment variables and steps.

[coderabbitai]

Walkthrough

The pull request introduces various updates across multiple files, including the .github/workflows/lint.yml, README.md, executor/README.md, go.mod, and several files within the challenger directory. Key changes include version updates for dependencies, modifications to the linting workflow by removing certain environment variables, and alterations to data types in several structures and methods to enhance consistency. Additionally, documentation has been improved for better clarity and readability.

Changes

File(s)	Change Summary
.github/workflows/lint.yml	Updated GOLANGCI_LINT_VERSION from v1.59.1 to v1.61.0; removed GOPRIVATE and GITHUB_ACCESS_TOKEN environment variables.
README.md, executor/README.md	Updated compatibility table for components; improved formatting and readability in documentation.
go.mod	Updated multiple dependencies to their latest versions; reverted google.golang.org/grpc to v1.65.0.
challenger/*.go, challenger/*.md	Changed data types for various fields and parameters from uint64 to int64 in multiple structs and methods.

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant CI/CD
    participant Linter
    participant Repo

    Developer->>CI/CD: Push changes
    CI/CD->>Linter: Run linting with updated version
    Linter->>Repo: Check code quality
    Repo->>CI/CD: Return results
    CI/CD->>Developer: Notify results

Loading

🐰 In the meadow, changes bloom,
A version here, a fix in gloom.
Dependencies dance, all aligned,
With clearer docs, we're more refined.
Hops of joy, let’s celebrate,
Code and bunnies, oh, how great! 🐇✨

---

📜 Recent review details

📥 Commits

Files that changed from the base of the PR and between 224dde7 and b768a62.

🔇 Files ignored due to path filters (1)

• go.sum is excluded by !**/*.sum

📒 Files selected for processing (63)

• README.md (2 hunks)
• challenger/README.md (2 hunks)
• challenger/challenger.go (2 hunks)
• challenger/child/child.go (2 hunks)
• challenger/child/deposit.go (1 hunks)
• challenger/child/handler.go (3 hunks)
• challenger/child/oracle.go (1 hunks)
• challenger/child/status.go (1 hunks)
• challenger/child/withdraw.go (4 hunks)
• challenger/host/deposit.go (1 hunks)
• challenger/host/handler.go (1 hunks)
• challenger/host/host.go (1 hunks)
• challenger/host/oracle.go (1 hunks)
• challenger/host/output.go (2 hunks)
• challenger/types/challenge.go (7 hunks)
• challenger/types/keys.go (2 hunks)
• client/client.go (1 hunks)
• db/types/utils.go (1 hunks)
• executor/README.md (4 hunks)
• executor/batch/batch.go (4 hunks)
• executor/batch/handler.go (8 hunks)
• executor/batch/status.go (1 hunks)
• executor/celestia/celestia.go (3 hunks)
• executor/child/child.go (3 hunks)
• executor/child/deposit.go (1 hunks)
• executor/child/handler.go (2 hunks)
• executor/child/oracle.go (1 hunks)
• executor/child/status.go (1 hunks)
• executor/child/withdraw.go (4 hunks)
• executor/executor.go (2 hunks)
• executor/host/batch.go (1 hunks)
• executor/host/deposit.go (1 hunks)
• executor/host/handler.go (1 hunks)
• executor/host/host.go (3 hunks)
• executor/host/oracle.go (1 hunks)
• executor/host/status.go (1 hunks)
• executor/host/withdraw.go (1 hunks)
• executor/types/batch.go (2 hunks)
• executor/types/config.go (3 hunks)
• executor/types/db.go (1 hunks)
• executor/types/query.go (1 hunks)
• go.mod (6 hunks)
• merkle/merkle.go (1 hunks)
• node/broadcaster/broadcaster.go (2 hunks)
• node/broadcaster/db.go (2 hunks)
• node/broadcaster/process.go (1 hunks)
• node/broadcaster/types/db.go (1 hunks)
• node/db.go (1 hunks)
• node/node.go (3 hunks)
• node/process.go (8 hunks)
• node/rpcclient/client.go (1 hunks)
• node/types/handler.go (2 hunks)
• node/types/status.go (1 hunks)
• provider/child/child.go (5 hunks)
• provider/child/msgs.go (5 hunks)
• provider/child/parse.go (3 hunks)
• provider/child/query.go (2 hunks)
• provider/child/tree.go (1 hunks)
• provider/host/host.go (3 hunks)
• provider/host/msgs.go (2 hunks)
• provider/host/parse.go (4 hunks)
• provider/host/query.go (7 hunks)
• types/math.go (1 hunks)

---

Note

🎁 Summarized by CodeRabbit Free

Your organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login.

🪧 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 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.

[sh-cha]

LGTM