fix store log removal from user Profile page

What does this MR do?

Fixes a loophole, when a bot removed a user from a pickup slot over the profile page - logging was avoided.

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

quite

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 (or userbot, works as well )
3. Sign up for a slot
4. Login as userbot
5. go to profile page of user
6. Remove user from slot (austragen)
7. Check fs_store_log that the steps where logged.

Screenshots (if applicable)

Any relevant screenshots if this is a design / frontend change

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

Es wurde eine Stelle in der Protokollierung bei dem Austragen von foodsavern aus Abholslots gefunden, die noch nicht erfasst worden war.