feat(docker): support structured OCI registry inputs for separate pull, push, and cache targets

[Copilot]

• Inspect the new review feedback on actions/docker/build-image
• Review the affected script block and current cache registry handling
• Move expression-based script inputs to environment variables
• Assert the cache registry is defined before generating registry cache configuration
• Run targeted validation for the touched files
• Run final review/security checks and reply to the new PR comments

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[neilime]

@copilot handle feedbacks

[Copilot]

@copilot handle feedbacks

Addressed the review feedback in d394437.

[neilime]

@copilot, dont mark original format for oci-registry-username, oci-registry-password and oci-registry as "legacy", this is the default mode, still relevant

[Copilot]

@copilot, dont mark original format for oci-registry-username, oci-registry-password and oci-registry as "legacy", this is the default mode, still relevant

Updated the wording so the scalar input form is described as the default format, and renamed the internal legacy markers to scalar, in 81b7db4.

[neilime]

@copilot handle feedbacks

[Copilot]

@copilot handle feedbacks

Handled in 6a40375.

[neilime]

@copilot handle feedbacks

[Copilot]

@copilot handle feedbacks

Handled in f00ebb6.

[neilime]

@copilot handle feedbacks

[Copilot]

@copilot handle feedbacks

Handled in 7b3ce1c.