fix: hide service name and port bindings weird behaviors

[ntorga]

1. We got a report that using port 8000 for example is being shown as Django. The service name is a purely aesthetic information that may led to confusion, so I think we should just hide it from the port bindings list for now as we won't be allowing people to customize the service names anytime soon;
2. When deploying a service with port 80 for http and other ports but also for http, the port bindings list on the front-end is only showing the 80. Here's the container for testing:

/var/infinite/ez container create --account-id 1003 --hostname testing.com --image-address nginx --port-bindings ssh:22:22/tcp --port-bindings http:80:80/http --port-bindings https:443:443/https --port-bindings unknown:3000:3000/tcp --port-bindings unknown:8000:8000/tcp --restart-policy always --profile-id 1

3. If the serviceName is not filled by the front-end, the port won't be exposed for some reason: https://i.imgur.com/X9LlfqC.png