Rework passport

What does this MR do?

• possibility to create the pdf and the passport separately in the user interface (setting is saved in localStorage on browser)
• added a calculated passport until valid date in region memberlist
• Refactored and tidy PassportGeneratorGateway and PassportGeneratorTransaction
• Use "QRCODE,H" in QR-Code for better error correction
• renamed in region memberlist tab "Ausweise" to "Ausweise & Verifzierung"
• removed role on passport
• The user passport page and a error container on dashboard now shows when it is no longer valid or how long it is still valid (days and date).
• Added filter dropdown in name/id search. Its possible to filter user with or without passport.
• It's only possible for the user to download a passport, if it has been activated or is valid.
• Adjusted modal text for verification and added modal for multiple user verification.
• The hint to the passport has been removed from the verification mail and inserted in a new passport bell and mail.
• the entry for the passport history is only added by the BOT. No longer by the Foodsaver itself.

How confident are you it won't break things if deployed?

Links to related issues

How to test

Screenshots (if applicable)

Checklist

• added a test, or explain why one is not needed/possible...
• no unrelated changes
• asked someone for a code review
• set a "for:" label to indicate who will be affected by this change
• set the "API change" label if changes in the API are not backward compatible
• added to the next milestone (see https://gitlab.com/foodsharing-dev/foodsharing/-/milestones, unless it has a "for:Dev" label)
• added an entry to CHANGELOG.md
• added a short text in the release notes to /release-notes/YYYY-MM.md
• Once your MR has been merged, you are responsible to create a testing issue in the Beta Testing forum: https://foodsharing.de/region?bid=734&sub=forum. Please change the MRs label to "state:Beta testing".
  • Consider writing a detailed description in German.
  • Describe in a few sentences, what should be tested from a user perspective.
  • Also mention different settings (e.g. different browsers, roles, ...) how this change can be tested.
  • Be aware, that also non technical people should understand.