Switch to lavalink's lavaplayer fork

[MichailiK]

This pull request...

• Fixes a bug
• Introduces a new feature
• Improves an existing feature
• Boosts code quality or performance

Description

Switches lavaplayer dependency from our fork to lavalink's fork.

It uses the (as of writing) latest commit instead of the latest stable version, as I've encountered lavalink-devs/lavaplayer#69 during my testing, which prevented playing any YouTube tracks.

Purpose

Fixes several issues related to our outdated fork, particularly the "Error loading track from YouTube (403)"

Relevant Issue(s)

Fixes #885

Maybe fixes #1291

And honestly, closes #1375 because switching to ffmpeg requires monumental effort & im pretty sure there's other music bots that do precisely that anyways.

[MichailiK]

The lavalink devs have added the ability to login to a Google/YT account to play age-restricted videos, and will display the following warning when no credentials have been provided:

[WARN] [YoutubeAccessTokenTracker]: YouTube auth tokens can't be retrieved because email and password is not set in YoutubeAudioSourceManager, age restricted videos will throw exceptions

Since one of JMusicBot's "core principles" is to not require any credentials except for a Discord bot token, I suppose we want to suppress this warning specifically? Or perhaps do give an option to let people enter credentials, while expressly discouraging it?

[jagrosh]

The lavalink devs have added the ability to login to a Google/YT account to play age-restricted videos, and will display the following warning when no credentials have been provided:

[WARN] [YoutubeAccessTokenTracker]: YouTube auth tokens can't be retrieved because email and password is not set in YoutubeAudioSourceManager, age restricted videos will throw exceptions

Since one of JMusicBot's "core principles" is to not require any credentials except for a Discord bot token, I suppose we want to suppress this warning specifically? Or perhaps do give an option to let people enter credentials, while expressly discouraging it?

I'm against including that functionality for 2 reasons. One is the intention to not require more than a bot token, but even more severe is that people should definitely not ever be including email and password in a config file. If we can suppress that warning, that would be preferable, because it's really bad practice to put passwords in plaintext and I don't want to confuse people into thinking that they should do that.

[jagrosh]

We can maybe revisit allowing the functionality in some roundabout way (ex, env variables or something else not in a plaintext config) but in general I don't want to have any messages advertising this, since it's really not a good practice in the first place.

[MichailiK]

I have just created a logback TurboFilter to suppress that specific message

[prashker]

Built MichailiK:fix/lavaplayer-fork-shenanigans from source and finally my MusicBot is back to life - just wanted to say thank you in advance!