Log status of port before starting server with SelfHostDeployer

[natemcmaster]

I'm trying to make it easier to determine if EADDRINUSE errors in our integration tests are caused because the port truly is in use or because there is some libuv problem binding to addresses.

cref aspnet/Entropy#209

[Tratcher]

Sample of the output?

[davidfowl]

Do we need this?

[davidfowl]

Do we need this?

[natemcmaster]

macOS with and without port in use

Windows with and without port in use

[davidfowl]

do you need to set linesLogged here too?

[natemcmaster]

stderr would indicate the lsof or netstat command failed to list port info or isn't available on the path.

[JunTaoLuo]

LGTM.

[mikeharder]

@natemcmaster: Looks like this is failing in our CI builds:

| ResponseFormats:WebListener:Clr:x64:Portable Warning: Failed to check port status. Executed: cmd /C netstat -nq | find "5087"
|                                                       Error: System.InvalidOperationException: The Process object must have the UseShellExecute property set to false in order to redirect IO streams.
|                                                          at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)
|                                                          at System.Diagnostics.Process.Start()
|                                                          at Microsoft.AspNetCore.Server.IntegrationTesting.PortHelper.LogPortStatus(ILogger logger, Int32 port)

It's just a warning but it's noise in the logs

[natemcmaster]

I'm going to revert this. It was an attempt to figure out what was causing port conflicts in tests, but it didn't help enough. I think we'll have more success if use dynamic ports.