Move away from Jitpack

[absurdlylongusername]

Checklist

• I made sure that there are no existing issues - open or closed - which I could contribute my information to.
• I have read the FAQ and my problem isn't listed.
• 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.
• I have taken the time to fill in all the required details. I understand that the feature request will be dismissed otherwise.
• This issue contains only one feature request.
• I have read and understood the contribution guidelines.

Feature description

Following on from discussion in Matrix chat, we need to replace Jitpack with something else that has the same functionality.

As explained in this article, Jitpack is barely maintained, obtuse, fragile, can break any time, and is potentially a huge security breach waiting to happen.

I am making this issue for us to decide on the best replacement.

@Stypox suggested using an manual implementation for getting builds directly from github in settings.gradle, which I think would be good.

My ideal solution would allow us to specify getting builds for a specific commit hash, but also allow us to get the latest commit for a specific branch.

Builds for commits on main branches (dev, master, etc.) should have the jars/binaries be able to be downloaded from online similar to Jitpack (e.g. packages published via CI build upon merge to a main branch), but other branches can have the repo fetched and built locally.

Probably we publish release versions to Maven central, and intermediate versions for each commit can be published to Github Packages, and then can use manual retrieval in settings.gradle to get individual commits from forks/PRs/etc.

Why do you want this feature?

Explained already

Additional information

No response