fix: handle port mappings with explicit IP bindings

[ravshansbox]

Summary

Fixes the "invalid publish IPv4 address" error when docker-compose.yml port mappings include explicit IP bindings (e.g., 127.0.0.1:5432:5432).

Changes

• Added composePortToRunArg() helper function in Helper Functions.swift that correctly parses Docker Compose port specifications into container run -p format
• Updated configService() in ComposeUp.swift to use the new helper instead of blindly prepending 0.0.0.0:
• Added 8 unit tests in HelperFunctionsTests.swift covering all port format scenarios

What was wrong

Previous code did:

runCommandArgs.append("0.0.0.0:\(resolvedPort)")

This produced invalid address 0.0.0.0:127.0.0.1:5432:5432 when the port spec already included an IP.

How it works now

The new parser intelligently handles all formats:

• 3000 → 0.0.0.0:3000:3000 (auto-completes)
• 8080:3000 → 0.0.0.0:8080:3000 (adds IP binding)
• 127.0.0.1:5432:5432 → 127.0.0.1:5432:5432 (preserves explicit IP)
• [::1]:3000:3000 → [::1]:3000:3000 (preserves IPv6)
• All with optional /tcp or /udp suffixes preserved

Testing

✅ All 70+ existing tests pass
✅ 8 new port conversion tests pass
✅ Build succeeds with no warnings

Closes #59

[Mcrich23]

I love this so much. Let me verify on my end and then we can get this merged!

[Mcrich23]

Thank you so much for fixing that. One more thing: can you please add a dynamic test for the full check bringing up the container?

Thank you!

[ravshansbox]

Implemented — I added a dynamic end-to-end test that brings the container up with an explicit IP port mapping and validates the full up/down lifecycle.

Details:

• Added testComposeUpWithExplicitIPPortMapping in Tests/Container-Compose-DynamicTests/ComposeUpTests.swift
• Verifies published ports are exactly 127.0.0.1:18081:80
• Runs ComposeUp (detached), checks container is running, then runs ComposeDown and checks container is stopped
• Included in commit 626f977

Thanks for the review.