feat (WIP): use pydantic for model validation

[NiceAesth]

Status: this branch will not function atm

Description

Pydantic is the industry standard tool for model validation. It is a well trusted tool baked into other libraries (such as FastAPI).

This PR aims to shift the library into using it. It will be a very big one, but I will attempt to keep commit history simple. Also, the models will try to keep the same structure as the interfaces used in Lavalink itself.

Reasoning

• It would be a massive gain towards stability and type safety
• It would provide very simple ways of handling versioned models using smart unions meaning we could remove a large portion of if statements for lavalink versions
• It would remove a massive amount of boilerplate we have to write
• Pydantic is ""blazing fast"" as the rust devs would say it

To-do:

Models:

• LavalinkVersion
• Events
• Enums
• Filters
• Payloads
• Track
• Playlist
• Queue
• Apple Music Song
• Apple Music Playlist
• Apple Music Album
• Apple Music Artist
• Spotify Track
• Spotify Playlist
• Spotify Album
• Spotify Artist

Library

• Pool
• Player

Code Style:

• Remove relative imports (this will be followed by a second PR to change the library to use poetry instead of pipenv, something which we arguably should have done in the first place as DX with pipenv for libraries simply sucks)
• Address type: ignore comments
• Address unused arguments in functions (e.g. force in disconnect())
• Separate concerns in player/pool better, reduce nesting
• Address inconsistencies between classmethod based defaults in Timescale filters and subclass based defaults with Frequency filters (e.g. Tremolo / Vibrato)

Documentation:

• wip idk

[NiceAesth]

Looking at the existing code the logic for tracks will become insanely simple by switching to typing based logic