feat: Patch Bundle Template with CI

[Ushie]

Feature description

Create a Patch Bundle template repository, with necessary CI for releases with support for this ReVanced/revanced-manager#572 format

Motivation

With the upcoming release of ReVanced Manager v2, it's about time to prepare Patch Bundles as a concept, currently Patch Bundles need to fork this repository and (optionally) remove existing patches

Acknowledgements

• This request is not a duplicate of an existing issue.
• I have chosen an appropriate title.
• All requested information has been provided properly.

[oSumAtrIX]

If we create a template repository, how do we keep changes in sync?

[Ushie]

A template repository gives you the base to start, but it isn't your base if that makes sense, maintainers can keep things as is or they must manually keep up with changes

However, I've found this action https://github.com/AndreasAugustin/actions-template-sync

[Ushie]

But that action won't help you migrate your own changes, there's no way around maintainers having to keep up with updates themselves

[oSumAtrIX]

What I mean is, say we bump ReVanced Patcher, now we would commit to the template repo as well as our patches repository.

[Ushie]

That's intended, it's possible to have something like the sync action that I mentioned above but that action won't automatically migrate the patches if something about the patch structure changes, ReVanced Patcher bumps may come with necessary changes to patches

[oSumAtrIX]

This is an annoying burden. Alternatively, a project template could be comited here. This way we'd be able to update the template at the same time

[Ushie]

How would you commit a template here?

[oSumAtrIX]

On second thought, this is too complex to realize, a template repository is easier.

[oSumAtrIX]

https://github.com/ReVanced/revanced-patches-template