Pass IPAM options when creating networks

[ousamabenyounes]

Summary

• Pass Compose networks.*.ipam.options through to Docker network creation.
• Add regression coverage for IPAM options without an IPAM driver or pool config.

Fixes #13785

Test verification (RED -> GREEN)

• Baseline: make test initially reported DONE 497 tests, 2 skipped, 1 failure; the pre-existing failure was pkg/watch TestGitBranchSwitch.
• RED: with only pkg/compose/create.go reverted, TestExecutePlanCreateNetworkWithIPAMOptions failed because opts.IPAM was nil instead of containing Options: {"ipam-option": "enabled"}.
• GREEN: go test ./pkg/compose -run TestExecutePlanCreateNetworkWithIPAMOptions -count=1 -v passed.

Full local suite

• Command: make test
• Result: passed with DONE 499 tests, 2 skipped after rebasing on latest main.

[glours]

A few changes to improve readability and avoid confusion between the two IPAM definition blocks.

[ousamabenyounes]

Addressed the review feedback in 7d1e1078e:

• built the IPAM object once in resolveOrCreateNetwork, including driver, config, and options, and removed the redundant second block
• made the executor network test constants shared across the sibling tests
• changed the IPAM option assertion values to ipam-option=enabled so they no longer collide with the project name

Rebased on latest docker:main and reran:

• go test ./pkg/compose -run 'TestExecutePlan(Empty|CreateNetwork|CreateNetworkWithIPAMOptions)$' -count=1
• make test -> DONE 499 tests, 2 skipped

[ousamabenyounes]

Rebased on current main and addressed the review feedback by keeping IPAM construction in one place and using distinct test values.

Local validation:

• go test ./pkg/compose -run "TestExecutePlan(Empty|CreateNetwork|CreateNetworkWithIPAMOptions)$" -count=1 -v
• make lint

[ousamabenyounes]

The failing check is e2e (standalone, oldstable) — it failed on the "Test standalone mode" step (exit code 2) with no test-level failure reported, while the plugin e2e variant passed on the same commit. This PR only touches createNetwork and its unit test (no e2e), so the failure looks unrelated to the change.

Locally against current main the package builds, go vet is clean, and go test ./pkg/compose/... passes — including TestExecutePlanCreateNetworkWithIPAMOptions.

Could a maintainer re-run the flaky e2e (standalone, oldstable) job? Happy to rebase on main if you'd prefer — thanks!

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!