chore(Dockerfile): use heredoc for build steps

[aofei]

See https://www.docker.com/blog/introduction-to-heredocs-in-dockerfiles/

[gemini-code-assist[bot]]

Summary of Changes

Hello @aofei, I'm Gemini Code Assist[^1]! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request modernizes the Dockerfile by implementing heredoc syntax for its multi-line RUN command. This refactoring aims to improve the clarity and maintainability of the Docker build process, making complex shell scripts within the Dockerfile easier to read and manage, aligning with contemporary Dockerfile best practices.

Highlights

• Dockerfile Refactoring: The primary RUN instruction within the Dockerfile has been refactored to utilize heredoc syntax.
• Improved Readability: This change significantly enhances the readability and maintainability of the Dockerfile by allowing multi-line shell commands to be written more cleanly without the need for explicit line continuation backslashes.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/release-build.yml

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with :thumbsup: and :thumbsdown: on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

[^1]: Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

[codecov[bot]]

Codecov Report

:white_check_mark: All modified and coverable lines are covered by tests. :white_check_mark: Project coverage is 93.98%. Comparing base (1ef7ce9) to head (8878a55). :warning: Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2510   +/-   ##
=======================================
  Coverage   93.98%   93.98%           
=======================================
  Files          34       34           
  Lines        9613     9613           
=======================================
  Hits         9035     9035           
  Misses        413      413           
  Partials      165      165           

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

:rocket: New features to boost your workflow:

• :snowflake: Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[xgopilot[bot]]

Code Review Summary

This is a well-executed refactoring that improves code maintainability and follows Docker best practices. The changes demonstrate:

✅ Strong adherence to Docker best practices - Heredoc syntax significantly improves readability over shell one-liners ✅ Proper error handling - set -eux flags ensure defensive programming
✅ Security maintained - No vulnerabilities introduced, multi-stage build pattern preserved ✅ Performance neutral or improved - Better layer caching with single RUN instruction

Overall: Approved - Ready to merge.

[aofei]

/cc @cpunion