Feature: new component for Mopidy Tidal created on Future 3

[reptilex]

I have created a component for mopidy tidal, it's in a way a very hacky because I'm using websockets and json rpc to call directly on mopidy services. Probably there are better ways to do this, but I might need a few hints to improve my current approach.

The current state and todos:

• manual mopidy card entries can trigger playing mopidy tidal songs, albums and playlists
• most methods of playermdp have been implemented in playermopidy
• there is a rudimentary copy of your thread usage in place
• there is a state poll function with threads (currently every 10 seconds)
• find out how to avoid lock of pulseaudio by mopidy
• create a bash installation script for mopidy tidal
• check whether this is the best approach or we should build on tidalapi on the jukebox (I could not figure out how gstreamer works, getting albums and playlists is easy but streaming ...)
• in case this approach is good enough discuss improvements of websocket and threading functionality
• improve on the state object and poll
• discuss how reconcile "player" functionality so that it is generic for mpd or mopidy-tidal, currently it's all based on folders
• check how to accomodate for webapp player functionality with rest of jukebox
• add mopidy tidal card creation on webapp (building on a zero is a pain)

Here is the draft pull request: #1901