Add `--no-tls` and `--port-routing` Flags to Enable Non-TLS Access and Port-Based Routing.

The current setup uses NGINX as a proxy, allowing only HTTPS access via subdomains. To increase flexibility and adaptability for different environments, add the following flags to the deploy command:

1. --no-tls: Disables TLS for all services, allowing access via HTTP or gRPC without encryption.
2. --port-routing: Enables access to services by specific ports instead of subdomains.

These options will make it easier to deploy services in internal or local environments.

Example Usage:

1. Default Setup (TLS with Subdomains):

   deploy
   

   Keeps the existing behavior with HTTPS access over subdomains.

2. Non-TLS HTTP and gRPC Access:

   deploy --no-tls
   

   Enables HTTP and gRPC without TLS, with subdomain routing.

3. Port-Based Routing Without TLS:

   deploy --no-tls --port-routing
   

   Configures services to allow HTTP and gRPC without TLS, with each service accessible on a specified port.

4. Port-Based Routing with TLS:

   deploy --port-routing
   

   Uses HTTPS but routes services via ports instead of subdomains.

Start by locating the deploy command and its NGINX configuration, then trace how TLS and subdomain routing are currently assembled. Implement and verify the four documented combinations of TLS and port routing, including HTTP and gRPC access where applicable.