Skip validation when extracting config variables

[scarab-systems]

What I did

• Allow unresolved Compose models used for variable discovery to skip validation while interpolation expressions are still present.
• Apply the same behavior to config --variables and remote-stack interpolation-variable prompting.
• Add regression coverage for templated typed port fields such as host_ip and published.

Related issue

Fixes #13613

(not mandatory) A picture of a cute animal, if possible in relation to what you did
![cute fuzzy animal]

Validation

• go test ./cmd/compose
• docker buildx bake lint

[glours]

/review

[docker-agent]

❌ PR Review Failed — The review agent encountered an error and could not complete the review. View logs.

[glours]

The fix looks correct, but I’d like us to add a regression test covering the up path as well.

The issue originally affects the remote-stack prompt flow used by up, so having coverage there would help ensure this does not regress again.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[scarab-systems]

Thanks for the review. That makes sense, and I appreciate the context on the up remote-stack prompt flow. I’ll add a focused regression test for that path.

[scarab-systems]

Added the focused up regression test in the latest commit. I also verified it locally with go test ./cmd/compose -count=1 and make lint.