Add ability to specify protocol on published ports in service and container create views

[ghost]

Is your feature request related to a problem? Please describe.
Currently, for published port links in the UI the http protocol is always prefixed. If the container requires https there is no way to specify this.

As previously discussed here, removing the default protocol and specifying it via the endpoint's public IP field is not a valid solution as it will be set on all services/containers and might need to be different for each.

Describe the solution you'd like
Add the ability to specify protocol when publishing ports via service and container create views and have Portainer create the published ports links in the UI with the specified protocols.

Example implementation

Additional info
Technical implementation of this feature is discussed in these comments:

• Problems about URLs under published ports #2721 (comment)
• Problems about URLs under published ports #2721 (comment)

[hhromic]

Thanks for opening this feature request. Appreciated.

I would like to mention that this might be still limited for the use case of Stacks deployed using a Docker Compose file. As far as I know, there is no way to add metadata to published ports. There would be no way for Portainer to know what kind of port is exposed by the service from a Stack Compose file.

However I think the user will still be able to manually associate the type of published ports after creating the Stack using the Services page (one by one). So the desired effect could still be achieved just not automagically from the Stack Compose file.

Not a big deal breaker imho but should be documented to avoid confusions.