If we receive an upgrade request after not upgrading, return redirect…

… and close connection (#108)

* If we receive an websocket upgrade after not upgrading redirect and close connection

* Include query in redirect

* Fix for 5.10

* Add test for closing conenction on unexpected upgrade

* Add detailed comment

Require hummingbird 2.14.0 (#105)

Require hummingbird 2.12.0 (#103)

Close timeout (#93)

* Add closeTimeout to websocket configuration

* Add testCloseTimeout

* Use swift-websocket 1.2.0

Split WS client from server (#87)

* Stage 1 - split into separate libraries internal to package

* Make WebSocketType internal

* swift format

* Use swift-websocket

* typo

* Remove all client code/tests

* Don't output docs for HummingbirdWS client/compression targets

* Update docs

* Temporarily use utf8-validation branch

* Add validateUTF8

* Use swift-websocket 0.1.0

* Remove InvalidUTF8Frame tests from 5.10

* Remove HummingbirdWSCore files

* Use swift-websocket 1.0

* Use Hummingbird 2.5

* Don't log inputClosed on upgrade as an error

Inconsistency in documentation brought up by docc v6 (#80)

Use Hummingbird 2.0 (#79)

Merge pull request #77 from hummingbird-project/dont-use-next-isolation

Don't use next(isolation:) as it has OS requirements

Fixes for Swift 6 mode and strict concurrency (#74)

Add testGracefulShutdown (#69)

* Add testGracefulShutdown

* Add XCT tests inside testGracefulShutdown