feat: add set code tx support

[colinlyguo]

Purpose or design rationale of this PR

This PR adds set code tx support in the convertTxDataToRLPEncoding function.

PR title

Your PR title must follow conventional commits (as we are doing squash merge for each PR), so it must start with one of the following types:

• feat: A new feature

Breaking change label

Does this PR have the breaking-change label?

• No, this PR is not a breaking change

Summary by CodeRabbit

• New Features

  • Improved transaction processing by adding dedicated handling for a new transaction type, leading to more accurate transaction encoding.

• Chores

  • Updated key third-party dependencies to enhance overall system compatibility and stability.

[coderabbitai]

Walkthrough

This update adds explicit handling for the SetCodeTxType transaction in the convertTxDataToRLPEncoding function by constructing a new transaction using types.NewTx with specific field conversions. Additionally, the dependency version for github.com/scroll-tech/go-ethereum is updated and the indirect status for github.com/holiman/uint256 is removed in the go.mod file to reflect direct usage. Error handling remains unchanged.

Changes

File(s)	Change Summary
encoding/da.go	Added a new case in convertTxDataToRLPEncoding for SetCodeTxType that creates a new transaction with fields populated via types.NewTx and uint256.MustFromBig conversions.
go.mod	Updated the version of github.com/scroll-tech/go-ethereum to a new commit and removed the // indirect comment from the github.com/holiman/uint256 v1.2.4 dependency declaration.

Sequence Diagram(s)

sequenceDiagram
    participant Caller
    participant EncodeFunc as convertTxDataToRLPEncoding
    participant TxCreator as types.NewTx

    Caller->>EncodeFunc: Call with txData (SetCodeTxType)
    EncodeFunc->>TxCreator: Construct new transaction with converted fields
    TxCreator-->>EncodeFunc: Return newly constructed transaction
    EncodeFunc-->>Caller: Return encoded transaction

Loading

Poem

I’m a bunny with a clever code hop,
New transactions now make my heart bop!
SetCodeTx jumps into the flow,
With each field in a rhythmic row.
Dependencies dance, leaping through the night,
Celebrating change with joy and delight!
🐇✨

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 6ab79d4 and 4749eff.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (1)

• go.mod (2 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• go.mod

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: tests

---

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.

[Thegaram]

Looks good, thanks! Let's merge after your 7702 PR was merged.

[colinlyguo]

Looks good, thanks! Let's merge after your 7702 PR was merged.

makes sense.

The base branch was changed.