Bump op-reth to v2.3.3

[Nazgolze]

Bumps op-reth v2.3.2 → v2.3.3 in reth/Dockerfile, with the commit pin resolved from the release tag. README updated to match.

Picks up the upstream fix for the eth_estimateGas bug after Karst activation. Rust toolchain unchanged (channel 1.94).

• op-reth: https://github.com/ethereum-optimism/optimism/releases/tag/op-reth/v2.3.3

Summary by CodeRabbit

• Documentation

  • Updated the README to reference the newer op-reth v2.3.3 release link and the corresponding source build reference.

• Chores

  • Updated the Docker build to pin op-reth v2.3.3 instead of v2.3.2, including the expected commit verification.
  • Refreshed the source build process to match the updated op-reth release.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: adb7b408-6dcb-46f9-96c2-d104902a3a43

📥 Commits

Reviewing files that changed from the base of the PR and between 7a94220 and 0de8004.

📒 Files selected for processing (1)

• reth/Dockerfile

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

• reth/Dockerfile

---

📝 Walkthrough

Walkthrough

Bumps the pinned op-reth version from v2.3.2 to v2.3.3 by updating the Dockerfile pin and verification steps, and updating the corresponding release link and source-tree URL in README.md.

Changes

op-reth v2.3.3 version bump

Layer / File(s)	Summary
Update op-reth version and commit pin reth/Dockerfile, README.md	ENV VERSION and ENV COMMIT now pin op-reth/v2.3.3; the clone verification and superchain-registry submodule step remain in the build flow; README links now point to v2.3.3.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• LiskHQ/lisk-node#123: Same op-reth pin update pattern across reth/Dockerfile and README.md.
• LiskHQ/lisk-node#129: Same files and same version-pin maintenance flow for op-reth.
• LiskHQ/lisk-node#131: Directly adjacent op-reth version bump in the same Dockerfile/README path.

Suggested reviewers

• sameersubudhi

Poem

🐇 A hop for v2.3.3,
In Docker and README, tidy and free.
The bunny peeks at the new commit glow,
Then skips along with a cheerful “go!” 🥕

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description summarizes the change, but it does not follow the required template and omits the problem and testing sections.	Rewrite the description using the template headings and add the issue number, implementation details, and how the change was tested.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: bumping op-reth to v2.3.3.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feature/plat-596

---

_{Comment @coderabbitai help to get the list of available commands.}