Add exception on failed port string parsing in BindingAddress.cs Resolves #24384

[h5aaimtron]

Add exception on failed port string parsing in BindingAddress.cs

This PR adds a FormatException in the BindingAddress.cs when an invalid portString cannot be parsed as int.

Description

Users have reported that when passing address strings containing invalid port strings is passed into BindingAddress.Parse(), instead of throwing an exception or generating a warning, the invalid port string is ignored, and the default ports (80/443) are applied. Invalid address strings such as "https://*:{abc}" should throw a FormatException due to the invalid port value 'abc' similar to how FormatExceptions are thrown for invalid hostnames.

Fixes #24384

[h5aaimtron]

@gfoidl I added some tests in the PR as well.

[h5aaimtron]

Additional changes will be required to handle NamedPipes. It is odd that the previous code worked as it set a port with named pipes, so will require further research.

[h5aaimtron]

While reviewing the test failures, I identified a pre-existing issue in the code. The port parsing code is wrapped in an if statement checking it is not a unix pipe, but fails to check if it is not a named pipe as well. This allowed named pipes to enter the port parsing code block, which combined with my earlier change, resulted in the thrown FormatException. Since named pipes do not have ports and therefore do not need to parse port numbers, I've added the not named pipe condition to the if statement to skip the code block for named or unix pipes.

[h5aaimtron]

Latest change fixes support for IPv6 [::1] binding. Test cases had non-bindable addresses marked as valid, so those were removed. For people looking simply to parse a Uri, they should use Uri.TryCreate(), not BindingAddress.Parse() as it infers a valid, bindable address, not just a valid uri.