Accept port 1 when validating published port ranges

The lower bound for a published port range was checked with a strict
greater-than, so port 1 was reported as an invalid range on both the host
and container sides. TCP and UDP port numbers start at 1.

Port 0 remains rejected, since it means "any port" rather than a specific
one.

Fixes #2014

Author: devops-thiago

Sources/Services/ContainerAPIService/Client/Parser.swift

@@ -701,13 +701,13 @@ public struct Parser {
             throw ContainerizationError(.invalidArgument, message: "invalid publish container port: \(containerPortText)")
         }
 
-        guard hostPortRangeStart > 1,
+        guard hostPortRangeStart >= 1,
             hostPortRangeStart <= hostPortRangeEnd
         else {
             throw ContainerizationError(.invalidArgument, message: "invalid publish host port range: \(hostPortText)")
         }
 
-        guard containerPortRangeStart > 1,
+        guard containerPortRangeStart >= 1,
             containerPortRangeStart <= containerPortRangeEnd
         else {
             throw ContainerizationError(.invalidArgument, message: "invalid publish container port range: \(containerPortText)")

Tests/ContainerAPIClientTests/ParserTest.swift

@@ -108,6 +108,15 @@ struct ParserTest {
         #expect(result[0].count == 1)
     }
 
+    @Test
+    func testPublishPortOne() throws {
+        let result = try Parser.publishPorts(["127.0.0.1:1:1/tcp"])
+        #expect(result.count == 1)
+        #expect(result[0].hostPort == UInt16(1))
+        #expect(result[0].containerPort == UInt16(1))
+        #expect(result[0].count == 1)
+    }
+
     @Test
     func testPublishPortInvalidProtocol() throws {
         #expect {