Chore: Rework workflows

[stumpylog]

Proposed change

Now that the actual image is decoupled from the build installers (thanks to the downloaded archive instead of being pulled from images), building the installers in another repo is a viable solution again. So this revives the old builder repo to build wheels and .deb on a manual dispatch. That should only need to happen every so often. Even less with dependabot being so broke...

• Pulls the installer archive from another repo, removing a bunch of binary files from this repo
• Removes a bunch of code from here
• I packaged our cleaner into an action (and used it in immich!), removing more code from here
• Consolidates the 2 docker jobs to 1
• Helper bash script isn't really useful now that default build args are set
• Upgraded the locked pipenv version. Lastest one seems stable
• In some future time, the builder packages and cache here can be removed and the cleaner can run against the other repo only

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Other (please explain) - CI maintence

Checklist:

• I have read & agree with the contributing guidelines.
• If applicable, I have tested my code for new features & regressions on both mobile & desktop devices, using the latest version of major browsers.
• If applicable, I have checked that all tests pass, see documentation.
• I have run all pre-commit hooks, see documentation.
• I have made corresponding changes to the documentation as needed.
• I have checked my modifications for any breaking changes.

[shamoon]

I dont pretend to fully understand every line of change here but overall seems like will yield big speed improvements to ci, etc. I really love the new image build instructions =)

Thanks as always for the persistent improvement

Edit (build worked perfectly fine for me, and quick)

[stumpylog]

There's at least some documentation over at the builder repo. But I would like to put some details together somewhere to help understand both the process here and the general architecture of paperless.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion or issue for related concerns.