Merging last three Beta Versions

Hi, this release merges the last three Beta releases.

• Lyrics and a few other attributes moved to extra sensor, for more read:
  https://github.com/KoljaWindeler/ytube_music_player/releases/tag/20211206.01
• Fixed Position reset on volume change, for more read:
  https://github.com/KoljaWindeler/ytube_music_player/releases/tag/20211209.01
• Adressed new app_id issue that made the player stop after the first track
  https://github.com/KoljaWindeler/ytube_music_player/releases/tag/20211212.02

Fix for new app_ids

This release fixes issues with new google chromecasts apps.
Basically that the player turned off after one track.

And renamed attributes

Fixed position reset on volume change

Quick fix for progress bar. Progress changed on volume update #153

Extra sensor / remove songs from playlist / sorting

Hi, this release will introduce a few features that were requested over the last 4 month.

Added features

1. New service: to remove songs from a playlist called remove_from_playlist. Create a button that will call the service and you can easily maintain your playlists (based on #153)
2. You can now choose if your media_browser results shall be sorted or just appear in the order of Youtube Music. Simply change that in the configuration menu of the integration. (Based on #141)
3. Introduction of the "extra" sensor, see below (Based on #124)

Breaking changes

This component will now add two entities: media_player.ytube_music_player (or renamed) and sensor.ytube_music_player_extra.
Some very big attributes have moved from the player to the sensor: lyrics, tracks, playlists, total_tracks and search.

The point of the extra sensor is, that you can deactivate it (-> configuration -> integration -> ytube_music_player -> configure -> more -> uncheck "Create sensor that provide extra information") to unclutter you "states" overview. It also gives me the option to add more stuff to the sensor (without flooding the media_player). E.g. search results. It is still super complicated to search for a track (call the search service) and play it (open the media_browser, go to the search results and start playing). Adding the search results to the sensor should make it easier for card-developers to add a card for that. Anyone interested in helping out?

This means that you may have to re-write some of your lovelace interfaces to utilize the sensor instead of the player now.

Autostop + Api Update

Feature

• ytube_music_player will detect an app change on a chrome cast (e.g. caused by a smartphone casting music to the chrome cast) and stop playing
• Bump up the version of the sub_api to fix an issue with albums not being available

This release merges the last beta into stable

Stop when different source starts casting

This is a Beta release to test the auto-stop function.
Use case was discussed here: #125
Please provide feedback.

Enhance 'Radio of...' options

I like to listen to radios, based on various inputs. So this release makes it a bit easier to start them.

New Features

• Added 'Radio of [current track]' to media_browser
• Added ytube_music_player.start_radio service for ease of use

Additional fixes

• Fixed option to expand Album tracks
• updated api to 0.19.0
• fixed error on player selection
• Removed 'all Tracks' from album menu

Merge Beta to stable

Merging the last three beta releases to stable.

Thumbnail with highest resolution

Added scanning for thumbnail with highest resolution
#119

Fixed missing player

Stick to single player if no dropdown is present
Should fix #117