[#1715] Added management command to delete expired contact invitations

[pi-sigma]

Taiga #1715

[codecov-commenter]

Codecov Report

Merging #787 (b770433) into develop (380ecd7) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           develop     #787      +/-   ##
===========================================
+ Coverage    93.15%   93.17%   +0.01%     
===========================================
  Files          719      721       +2     
  Lines        24982    25027      +45     
===========================================
+ Hits         23273    23318      +45     
  Misses        1709     1709              

Files	Coverage Δ
...accounts/management/commands/delete_invitations.py	100.00% <100.00%> (ø)
src/open_inwoner/accounts/models.py	97.13% <100.00%> (ø)
src/open_inwoner/accounts/tests/test_commands.py	100.00% <100.00%> (ø)
src/open_inwoner/conf/base.py	95.62% <100.00%> (ø)
src/open_inwoner/utils/logentry.py	100.00% <ø> (ø)

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[Bartvaderkin]

Let's add a message to extra_data here so this record means something in the admin list view.

Which is why we don't create TimelineLog objects directly but use one of the helpers from open_inwoner/utils/logentry.py that add a bit more information in semi-standardized fields (in this case probably system_action()).

If you want to store more info on it you can add a **kwargs that adds additional fields to the extra_data. In this case the extra info should probably have both the inviter and invitee, or the record would not be that useful. (eg: if a user complains their invites disappeared, can we retrieve anything from just the invitee/recipient and a date?)

You could also choose to log per inviter and set them as the user in the TimelineLog.