CommonClient: Port Casting Bug

[qwint]

What is this fixing or adding?

when a port is used to connect in CommonClient that cannot be cast to an int urllib.parse() throws an exception that is uncaught and puts the client into an invalid state where the port can never be updated to be valid without closing the application.
This adds a try/catch for that does not set the port when not a valid int, which causes downstream code to error and handle the disconnect gracefully.
I think a prettier solution would be much better, since this adds a lot more error messages that hide the actual issue, but at least this allows you to retry a connection.

How was this tested?

using ports with spaces (i.e. "123 ") full text ports (i.e. "asdf") and valid ports (i.e. "123") and making sure an error was thrown when the port was invalid, and a connection was attempted when the port was valid. And then confirming that the port could be changed and a new connection attempted

Note: testing on py 3.8 seems to automatically trim the whitespace (and thus not throw the Exception) but this still handles a full text port.

If this makes graphical changes, please attach screenshots.

[qwint]

new visuals after i moved the port setting down to just reuse the later 'try' block because i wanted to be raising the error there anyways

[agilbert1412]

seems like a simple enough one liner for better user experience

[beauxq]

looked at code - including the implementation of the port property