soReusePort socket option fails on windows

[ondrejhavelka]

Describe the bug

On Windows, the blaze server wants to set the SO_REUSEPORT socket options which is not available and it fails when the server accepts a request and sets the sockets options on sun.nio.ch.SocketChannelImpl#setOption

The bug was introduced within #607

To Reproduce

Run the server on any windows machine and make a request

Additional context

java.lang.UnsupportedOperationException: 'SO_REUSEPORT' not supported
	at java.base/sun.nio.ch.SocketChannelImpl.setOption(SocketChannelImpl.java:215)
	at org.http4s.blaze.channel.nio1.NIO1ClientChannel.$anonfun$configureOptions$1(NIO1ClientChannel.scala:48)
	at scala.collection.immutable.Vector.foreach(Vector.scala:1856)
	at org.http4s.blaze.channel.nio1.NIO1ClientChannel.configureOptions(NIO1ClientChannel.scala:47)
	at org.http4s.blaze.channel.nio1.NIO1SocketServerGroup.org$http4s$blaze$channel$nio1$NIO1SocketServerGroup$$handleClientChannel(NIO1SocketServerGroup.scala:302)
	at org.http4s.blaze.channel.nio1.NIO1SocketServerGroup$SocketAcceptor.acceptNewConnections(NIO1SocketServerGroup.scala:181)
	at org.http4s.blaze.channel.nio1.NIO1SocketServerGroup$SocketAcceptor.opsReady(NIO1SocketServerGroup.scala:150)
	at org.http4s.blaze.channel.nio1.SelectorLoop.processKeys(SelectorLoop.scala:195)
	at org.http4s.blaze.channel.nio1.SelectorLoop.org$http4s$blaze$channel$nio1$SelectorLoop$$runLoop(SelectorLoop.scala:165)
	at org.http4s.blaze.channel.nio1.SelectorLoop$$anon$1.run(SelectorLoop.scala:59)
	at java.base/java.lang.Thread.run(Thread.java:829)```

[jakubjanecek]

Hi. You can set the option to false and that should resolve your problem. Is that ok?

[ondrejhavelka]

unfortunately no,
the problem is the missing feature on Windows and it fails regardless of the value
it tries to set an option that is not available on Windows

we discuss it with @sideeffffect on slack and it a bug in SST

I also tried the example application and it also fails

[ondrejhavelka]

from debugging

[jakubjanecek]

Right, I remember thinking about this but I haven't realized that these wouldn't be supported at all, I thought just reasonable default value would be enough. Anyway, I've created a PR to fix this.