Unicorn-binance-websocket-api

Changed
- Loglevels
Fixed
- Fixed double slash bug when getting listen key for userDataStream.
[PR 87](https://github.com/LUCIT-Systems-and-Development/unicorn-binance-websocket-api/pull/87)
- Fixed RuntimeError in connection row 243 (added restart)

Fixed
- restart if "with connection" in socket gets closed
- exception json.decoder.JSONDecodeError: respond = request_handler.json()

Fixed
- Exception AttributeError Info: module 'asyncio.base_futures' has no attribute 'InvalidStateError' [issue 72](https://github.com/LUCIT-Systems-and-Development/unicorn-binance-websocket-api/issues/83)

Fixed
- exception in `print_suammary()`

Added
- stream_buffer control: create_stream(channels, markets, stream_buffer_name=None):
If `False` the data is going to get written to the default stream_buffer, set to `True` to read the data via
`pop_stream_data_from_stream_buffer(stream_id)` or provide a string to create and use a shared stream_buffer
and read it via `pop_stream_data_from_stream_buffer('string')`.
- `add_to_ringbuffer_error()`
- `add_to_ringbuffer_result()`
- `set_ringbuffer_error_max_size()`
- `set_ringbuffer_result_max_size()`
- `get_errors_from_endpoints()`
- `get_results_from_endpoints()`
- `get_ringbuffer_error_max_size()`
- `get_ringbuffer_result_max_size()`
Changed
- renamed `restart_stream()` to `_restart_stream` and execute it only with a valid restart_request
Fixed
- Ensure that during a restart, only the recent thread is able to send the payload for subscription

Added
- psutil (new requirement)
- exception handling of `websockets.exceptions.InvalidMessage` [issue 72](https://github.com/LUCIT-Systems-and-Development/unicorn-binance-websocket-api/issues/72)
- general exception handling
- show threads, memory and cpu usage in `print_summary()`
- `get_process_usage_memory()`
- `get_process_usage_cpu()`
- `get_process_usage_threads()`
Fixed
- Close WS only if open in connection class row 190 [issue 72](https://github.com/LUCIT-Systems-and-Development/unicorn-binance-websocket-api/issues/72)
Removed
- some code in connection row 206 which is not needed anymore and is causing a coroutine error
- `is_websocket_uri_length_valid()`