Adding service for paperless

[martonsz]

fulfills: #2349

This service is using a workaround for the issue mentioned here: #2572
Notice how the entrypoint is replaced with a script that removes the forward slash from the env variable PAPERLESS_URL.

The environment variable for PAPERLESS_SECRET_KEY is set using the awkwardly named SERVICE_PASSWORD_64_PAPERLESSSECRETKEY. But if I used the name SERVICE_PASSWORD_64_PAPERLESS_SECRET_KEY it would not show up in the web GUI.
Tested in branch next ~v4.0.0-beta.307 (in dev mode using spin up).

[SpuriousGer]

Excellent, thank you!

[compgeniuses]

HEllo @martonsz i am curious, does paperlessNGX work without the availability of gotenberg?

the latest version of paperless uses gotenberg 8.7

[martonsz]

I have never used Gotenberg with Paperless. It is an optional service.

I have used Paperless since paperless-nx (without the 'x') without knowing what Gotenberg is. I googled it just now 😁

I always convert my documents to PDF manually. I don't trust auto converters 😏 because you never know what comes out on the other end. Maybe I should try Gotenberg...

The docker compose in this PR does not include the Gotenberg service.

[gitguardian]

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
Once a secret has been leaked into a git repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.

---

^{_{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}}

[peaklabs-dev]

Thank you for the PR 💜. I will test and fix it if needed.

[peaklabs-dev]

Just for information, the workaround is no longer needed as we have introduced a new parser that fixes this problem.