Huge thanks to @stuartcamerondeakin For his PR to remove Starscream. This PR has been made on top of his PR.

Starscream has been removed 🥳

The note inherited from @stuartcamerondeakin 's PR:

The starscream library doesn't correctly report an initial connection failure to the SwiftStomp when using the default TCPTransport.swift transport library, and despite there being two pending PRs daltoniam/Starscream#904 and daltoniam/Starscream#821 which both attempt to address the issue neither has been merged for 3 and 4 years each respectively. Hopes of this being resolved any time soon are not high.
This makes use of SwiftStomp in a production environment where connectivity needs to be ensured with adequate retries etc impossible.
The alternative if running on iOS 13+ is to use the NativeTransport.swift library internally, but that's just a very thin wrapper for Apple's URLSessionWebSocketTask, making the use of Starscream itself fairly redundant.
I've therefore removed the dependency on Starscream and have implemented the underlying WebSocket transport natively using URLSessionWebSocketTask. Surprise 🎉!
This is a big PR but makes the library much more robust, simplifies some things and removes the dependency on Starscream which seems to have always been problematic at best.
Cases that have been tested:
- Initial connection failure to the websocket with automatic reconnection enabled works
- Connection drops on an existing connection also result in automatic reconnection attempts
- Messages are being sent to topics correctly and subscription continues to work as-is
- SPM dependency works, cocopods dependencies are not tested as we don't use that

Upstreams supports 😎

Now we can consume events, messages, and receipts using the upstream publishers. This is super useful when we want to use SwiftStomp in SwiftUI's projects.