Remove baskets when a user gets deleted

Closes #983 (closed)

What does this MR do?

Sets the status of all active baskets to 'deleted' if a user is deleted.

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

Very sure

Links to related issues

Any relevant links (issues, documentation, slack discussions).

How to test

Steps a reviewer can take to verify that this MR does what it says it does e.g.

1. Checkout branch locally
2. Login as foodsaver
3. Create a basket and remember the ID
4. Delete the user
5. Login with another user
6. Try to access the basket using the ID -> it should be deleted

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
• use "state:" labels to track this MR's state until it was beta tested
• added an entry to CHANGELOG.md
• add a short text that can be used in the release notes
• Once your MR has been merged, you are responsible to create a testing issue in Beta Testing Repo:
  • 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.

Release notes text

Wenn ein Account gelöscht wird, werden auch alle zu diesem gehörenden und noch offenen Essenskörbe gelöscht.