Improve docker build performance

[Warashi]

What this PR does:

Build a Go binary with the host platform using the GOOS/GOARCH option and copy it to the target container image.
ref; https://docs.docker.com/build/building/multi-platform/#cross-compiling-a-go-application

Why we need it:

We sometimes face build failure at go build. I think this comes from QEMU and Go combination. So I changed the Dockerfile to build go binary without QEMU.
https://github.com/pipe-cd/pipecd/actions/runs/13126728528/job/36624384578#step:8:1

Which issue(s) this PR fixes:

Maybe fixes #5548

Does this PR introduce a user-facing change?: No

• How are users affected by this change:
• Is this breaking change:
• How to migrate (if breaking change):

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 26.41%. Comparing base (de1800e) to head (1b95b05).
Report is 281 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #5549      +/-   ##
==========================================
- Coverage   26.42%   26.41%   -0.01%     
==========================================
  Files         465      465              
  Lines       49907    49907              
==========================================
- Hits        13189    13185       -4     
- Misses      35663    35666       +3     
- Partials     1055     1056       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[khanhtc1202]

👍

[ffjlabo]

@Warashi
So we don't need the QEMU setup in the workflow?
https://github.com/pipe-cd/pipecd/blob/75db0fad0eb9d6a08914a73a003f455442a42c38/.github/workflows/publish_image_chart.yaml#L66C1-L70C91

[Warashi]

@Warashi So we don't need the QEMU setup in the workflow? https://github.com/pipe-cd/pipecd/blob/75db0fad0eb9d6a08914a73a003f455442a42c38/.github/workflows/publish_image_chart.yaml#L66C1-L70C91

@ffjlabo Thank you for your comment.
We still need QEMU because some multi-stage builds that have no platform options are run on QEMU.
We have to run them on QEMU because the final image must be built on the same platform as the image's platform.

[ffjlabo]

Sorry, I forgot to approve 🙏 LGTM