fix: add a name (http) to the service port

[lance]

I'm not sure if we should provide a configuration option for this or not. I'm also not sure what the behavior would be if some other value was already specified in a .nodeshift/service.yml file.

fixes #183

[coveralls]

Coverage remained the same at 96.078% when pulling 2439540 on 183-add-name-to-service-port into bd3f10b on master.

[lholmquist]

i would say we probably don't need this to be configurable, since it is really just a label(I think).

I think if someone had the ports section in a .nodeshift/service.yml it would merge it using the https://lodash.com/docs/4.17.5#merge function.

I'm not really clear on what the other protocols would be to have multiple ports, this was basically a copy/paste from another example.

[lance]

@lholmquist I think this is really just a name, so that if a service has multiple ports they can be disambiguated within a route. I'm going to go ahead and merge this.