feat: use go 1.22

[Thegaram]

1. Purpose or design rationale of this PR

...

2. 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:

• build: Changes that affect the build system or external dependencies (example scopes: yarn, eslint, typescript)
• ci: Changes to our CI configuration files and scripts (example scopes: vercel, github, cypress)
• docs: Documentation-only changes
• feat: A new feature
• fix: A bug fix
• perf: A code change that improves performance
• refactor: A code change that doesn't fix a bug, or add a feature, or improves performance
• style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
• test: Adding missing tests or correcting existing tests

3. Deployment tag versioning

Has the version in params/version.go been updated?

• This PR doesn't involve a new deployment, git tag, docker image tag, and it doesn't affect traces
• Yes

4. Breaking change label

Does this PR have the breaking-change label?

• This PR is not a breaking change
• Yes

Summary by CodeRabbit

• Chores
  • Upgraded the underlying Go programming language to version 1.22 across build pipelines and container configurations.
  • Standardized and modernized build environments to ensure improved stability and compatibility for production releases.

[coderabbitai]

Walkthrough

This pull request updates the Go version from 1.21 to 1.22 across various CI and build configurations. The GitHub Actions workflow file and multiple Dockerfiles have been modified to use the newer base images that reference Go 1.22. Additionally, the module file (go.mod) now reflects the updated Go version. No changes have been made to the underlying logic or control flow.

Changes

File(s)	Change Summary
.github/workflows/l2geth_ci.yml	Updated Go version from 1.21.x to 1.22.x in multiple CI job definitions.
Dockerfile, Dockerfile.mockccc	Updated base image from scrolltech/go-rust-builder:go-1.21-rust-nightly-2023-12-03 to scrolltech/go-rust-builder:go-1.22.12-rust-nightly-2023-12-03.
Dockerfile.alltools, Dockerfile.mockccc.alpine	Updated base image from golang:1.21-alpine to golang:1.22-alpine (builder stage).
go.mod	Updated module Go version from 1.21 to 1.22.

Possibly related PRs

• ci: add zizmor #1146: The changes in the main PR, which update the Go version in the CI workflow, are related to the changes in the retrieved PR that also involve modifications to the .github/workflows/l2geth_ci.yml file, specifically regarding the workflow's structure and permissions, indicating a connection at the code level.

Suggested reviewers

• colinlyguo
• georgehao

Poem

I'm a coding rabbit on a merry spree,
Hopping through files to set our version free.
From 1.21 to 1.22 the changes gently flow,
Each Docker and module now in a fresh new glow.
With joyful leaps, our build-up starts to grow! 🐇

Tip

⚡🧪 Multi-step agentic review comment chat (experimental)

• We're introducing multi-step agentic chat in review comments. This experimental feature enhances review discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments.
  - To enable this feature, set early_access to true under in the settings.

---

📜 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 650a5dd and 77f8325.

📒 Files selected for processing (2)

• Dockerfile (2 hunks)
• Dockerfile.mockccc (1 hunks)

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

• Dockerfile.mockccc
• Dockerfile

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

• GitHub Check: test
• GitHub Check: Analyze (go)

---

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