Remove cascading deletion between meeting user and motion relations

[luisa-beerboom]

Closes #3105
Needs OpenSlides/openslides-meta#325

[vkrasnovyd]

Looks good. Is there a reason why you didn't add motion_working_group_speaker and motion_editor to the user.delete tests?

[luisa-beerboom]

Looks good. Is there a reason why you didn't add motion_working_group_speaker and motion_editor to the user.delete tests?

Because they're already tested via the meeting_user test

[Elblinator]

works as intended but needs adjustements in the client

[Elblinator]

if motion is forwarded then the submitter are not cottectly copied
used users for copy:

fowarded motion:

payload

action: "motion.create_forwarded"
mark_amendments_as_forwarded: false
meeting_id: 2
origin_in: 5
reason: ""
text: "<p>u</p>"
title: "u"
use_original_number: false
use_original_submitter: true
with_amendments: false
with_attachments: false
with_change_recommendations: false

result

{
  "status_code": 200,
  "success": true,
  "message": "Actions handled successfully",
  "results": [
    [
      {
        "id": 7,
        "sequential_number": 2,
        "non_forwarded_amendment_amount": 0,
        "amendment_result_data": []
      }
    ]
  ]
}

[Elblinator]

see above

[luisa-beerboom]

I am guessing you would want it to say Deleted user, a (Test structure level a), Administrator (Test structure level).
Should Deleted user be translated in accordance with the meetings language?

[Elblinator]

Ye, please translate \o/

[vkrasnovyd]

Looks good and well covered with tests.