Add invidious companion support

[unixfox]

Description

Invidious companion is the new tool created for the retrieval of the YouTube streams: https://github.com/iv-org/invidious-companion

Invidious will not handle the videos streams retrieval anymore, as it has become a burner for the Invidious team to adapt. Instead, invidious companion will be based on https://github.com/LuanRT/YouTube.js which is the most up to date when it comes to video streams retrieval.

This allows us to spend more time on actually improving the Invidious frontend.

What does this PR do?

Invidious send the /player request to Invidious companion in HTTP(S). Invidious companion does all of its magic then Invidious does the usual parsing of the player endpoint.

Invidious also delegate the work of latest_version, /api/manifest/dash/id and /videoplayback to Invidious companion.

What does invidious companion do

• You can set multiple invidious_companion. Allowing you to utilize multiple external servers
• It supports SOCKS proxy - related to Allow to use proxies (HTTP(s) & socks) #301
• There is a plan to support multiple proxies: handle the ability to use multiple proxies invidious-companion#5
• There is no need to use inv_sig_helper as the program automatically handle the deciphering.
• There is no need for youtube-trusted-session-generator as the program automatically generate a po_token at a configurable frequency.
• You can logging with a yt account

Incompatibilities

• You can't use inv_sig_helper with invidious companion

Not supported yet - will be work in progress after this PR is merged

• The Invidious API is not fully supported. At least, if companion and invidious are not using the same "public" IP address, this won't work. Issue [Enhancement] Support Invidious API invidious-companion#22
• Download feature is not supported. Issue invidious: support download function invidious-companion#13

Future potential work

• Have Invidious proxying the requests to Invidious companion in order to make it easier for beginners.

How to try?

Official test docker image for Invidious with this branch "invidious-companion" is available at quay.io/invidious/invidious:companion and quay.io/invidious/invidious:companion-arm64

1. Run Invidious companion with a secret key: https://github.com/iv-org/invidious-companion?tab=readme-ov-file#run-locally
2. Configure Invidious companion in the config.yaml and with the same secret key:

invidious_companion:
  - private_url: "http://localhost:8282/"
    public_url: "http://localhost:8282/"
invidious_companion_key: hoMyBeautifulKey

3. Run Invidious

Fixes

• Fixes [Bug] "This helps protect our community." - "Please sign in to confirm you’re not a bot" #4734 - Any new issue around YouTube breaking the /player will know have to happen on https://github.com/iv-org/invidious-companion/issues
• Fixes [Enhancement] Add support for multiples audio tracks #2007 - youtube.js provide DASH files with multi audio support
• Fixes [Bug] Auto-generated subtitles no longer display in the video player #4660 - youtube.js provide the captions
• Fixes [Feature request] Add option to sign in to Google account (as workaround for "Please sign in" blocking playback) #4977 - youtube oauth is available thanks to youtube.js
• Fixes [Bug] DASH on Safari iPadOS is broken - Playback cannot continue. No available working or supported playlists. #2720 - dash manifest generated works with ipadOS
• To investigate: [Bug] DASH quality on safari iOS #2236
• To investigate: [Feature request] Add support for transcripts #2564
• To investigate: [Enhancement] Throw an error on Widevine content #3021

Related to

• [Enhancement] Print message about guide on how to configure invidious companion when "This helps protect our community." message is found #4838

[unixfox]

Feedback from @Fijxu:
Try to handle busted or IP blocked invidious companions.

[unixfox]

I have just added a new commit for giving invidious companion the ability to verify that the request originated from an invidious watch page.

This allows to combat against bots that will abuse the latest_version endpoint. This verification is not enabled by default in Invidious companion.

I made it on purpose to not include the verification ID for the internal latest_version redirect. Mainly because this would defeat the purpose of combatting bots since the ID would be given by Invidious.

[unixfox]

I just marked this PR as ready as I think the code is now production ready.

@SamantazFox @syeopite could you please take a look again at the code? Thanks.

[unixfox]

note: there is technically no need to store some kind of baseUrl from companion since we already have this info in "public_url" parameter from config.yaml
(idea from @Fijxu)

and we could remove this too in invidious companion

[syeopite]

Suggested change

	# Proxy needs to be reinstated every time we get a client from the pool
	conn.proxy = make_configured_http_proxy_client() if CONFIG.http_proxy

[syeopite]

Suggested change

	next make_client(companion.private_url, force_resolve: true)
	next make_client(companion.private_url, use_http_proxy: false)

[syeopite]

Suggested change

	conn = make_client(companion.private_url, force_resolve: true)
	conn = make_client(companion.private_url, use_http_proxy: false)