API deployment - port restrictions not enforced

[Nanashi-lab]

Description:

The API deployment process currently allows users to specify any port number under host (localhost:[portnumber]), including invalid ones, during deployment. However, only port 9006 functions correctly. Deploying to other ports results in various errors. It also allows for the deployment of port numbers exceeding the valid range (1-65535).

Deploy an API - Deployment to all port succeeds from backend.

Current Behavior:

• Connecting to deployment to port 9006 succeeds.
• Connecting to deployment to port 9005 results in an error: "not found".
• Connecting to deployment to port 9007 results in the error: "Error invoking remote method 'send-http-request': Error: Parse Error: Expected HTTP/".
  -Connecting to deployment to port any other port results in the error: "Error invoking remote method 'send-http-request': Error: connect ECONNREFUSED 127.0.0.1:9008".
• Deployment to port 100000000 allows the deployment to proceed, which it should not, as it's outside the valid port range.

[vigoo]

We no longer require specifying the localhost:9006 when deploying to a local golem instance, so I'm closing this.