test cleanup: turf special handling of jetty port already in use exception

[lread]

Currently

Our tests include special handling to quiet a Jetty exception for a port being already in use. Jetty could throw this when asking it to choose the port.

But...

We've since upgraded ring usage in our tests which upgraded us from Jetty 7 to Jetty 9.
Maybe Jetty no longer throws this exception in this case?

I've not been able to trigger this exception with multiple test runs.

So...

I'll delete the special handling for our tests.

If I've missed the case that would trigger this exception today, we can always add the special handling back in.