Transition to official YouTube API

[Dorge47]

Reliance on Dorge47/YouTubeAPI is subject to failure every time YouTube changes their frontend, as they did in 2022. Reliance on Holodex is subject to failure when their systems go down, which is a lot more often than YouTube does. Current implementation of the screwy YouTube API and the Holodex API send far too many requests for YouTube's official API quota so efforts will need to be made to either reduce API usage or request a quota increase.

• Map hypothetical quota requests #5
• Reduce quota usage or request quota increase #6
• Fallback to screwy API or Holodex if YouTube is unavailable or increased quota is reached

[Dorge47]

This may be abandoned if YouTube rejects a quota limit increase.

[Dorge47]

The more I work with the existing API, the more strongly I feel that it fits my needs better than the official YouTube API. The official API currently lacks a way to determine whether a video is a livestream, a short, or a traditional video. Scraping the HTML content, on the other hand, gives us data like isLiveContent, which is a boolean that indicates exactly what it says on the tin. Even shorts can be detected by checking a video ID against the channel's auto-generated "Short videos" playlist (where the playlist ID is obtained by replacing the leading UC in a channel ID with UUSH). If a game-changing use case for the official API is not found within the next few months, a hybrid system will be adopted wherein the official API is used where extra data (like whether a video is a livestream or a short) is not needed, but my API is used for everything the official API cannot do. This maintains a balance between only using my API, which would eventually get me rate-limited, and only using the official API, which wouldn't provide the information I need.