Migrate project dependencies to using Version Catalogs

[snaik20]

Checklist

• [X] I made sure that there are no existing issues - open or closed - which I could contribute my information to.
• [X] I have read the FAQ and my problem isn't listed.
• [X] I'm aware that this is a request for NewPipe itself and that requests for adding a new service need to be made at NewPipeExtractor.
• [X] I have taken the time to fill in all the required details. I understand that the feature request will be dismissed otherwise.
• [X] This issue contains only one feature request.
• [X] I have read and understood the contribution guidelines.

Feature description

Currently, the project manages dependencies by declaring them directly within the build.gradle file. This approach, while functional, can become cumbersome and difficult to maintain as the project grows and the number of dependencies increases.

This feature proposes migrating dependency management to Version Catalogs. Version catalogs are a centralized location within the Gradle build system to store and manage all project dependencies.

Why do you want this feature?

Version catalogs offer several advantages over declaring dependencies directly in build.gradle: https://developer.android.com/build/migrate-to-catalogs

Additional information

No response