Migrate ServerDiscovery into the SDK

[JPKribs]

Summary

Per: jellyfin/Swiftfin#1533

Moves the ServerDiscovery logic into the SDK instead of being in Swiftfin. Introduces a new dependency for the SDK in:

https://github.com/apple/swift-nio-transport-services

Questions

1. I ran into this NIO issue. There is zero impact from those errors except for the "error" logs. I've resolved the "errors" by manually finding the IPv4/IPv6 with a get func and ifaddr. The downside of manually getting the IP is we only broadcast on one IP instead of binding to all interfaces. I would prefer we take the 0.0.0.0 & :: route instead of using these get funcs since that gives us a more robust approach and reduces the total code for this PR. The current version of this uses the get funcs but I'd be happy to change this if we are fine with those errors getting logged.
2. When this was in Swiftfin, I was using the logger. I changed this to just print() the same messages to the terminal. I was considering os.log but I saw that required a version bump for MacOS. Whatever approach we want I can make changes. The log prints aren't necessary so worst case I can just delete all the prints.

[JPKribs]

If you want to test, this branch is all configured ready to go. Currently pointed at my branch until we have our next release:

• Use Server Discovery from SDK Swiftfin#1533

[JPKribs]

I think it would make sense to knock out #46 before this one. I'm happy where this one stands but I was able to do this same network discovery using Foundation and Network. I only used NIO since I thought I was going to use it for the WebSocket.

If we end up using my current version of the WebSocket where I don't use NIO, it would make more sense to me to redo this one but using non-NIO to avoid adding the dependency unnecessarily.

If we decide we want to use NIO for the WebSocket, we can keep this as-is but I think WebSocket should dictate NIO instead of this.