Host routing pattern not match when host contains port #3036

[ashraf-revo]

fix #3036

[aaHomeOfficeGit]

In our env we are running SCG on non standard ports like 9443 or 8089. When the client makes a call the HTTP header Host has the value which includes the non-standard port number like fqdn:9443

Until 4.1.0 scg version the host predicate definition had to include the comma separated list of fqdn1:9443,fqdn2:9443.

In a simple case the port number matching may make no sense, but there are cases when let say a https offloading rev proxy is shielding the scg, and the that rev proxy may even have listeners on multiple ports forwarding to the same scg. Let say the scg is listening on let say a 8090 port, but this port will never been seen by a client. In this case the scg may want to have a route which matches to a specific Host header's port. E.g fqdn:9443->service1.v1, fqdn:10443->service1.v2.
This port number based routing option is no longer possible with 4.1.0.

May be a new predicate would be better for Port on Host http header? ... except the Host header may not always have port number (I would need to check the specs)
Or may be the host predicate could check matching for: inetaddr.host and inetaddr.host+":"+inetaddr.port at the same time? ...