Remove the meeting_user when removing a user from a meeting

[luisa-beerboom]

Closes #2111
See OpenSlides/openslides-meta#347

• user.update now deletes the meeting user when the group_ids are emptied. (Uses custom meeting_user.delete class bc using the actual one would cause circular dep exceptions)
• motion.create doesn't automatically assign the calling user anymore. The chosen submitters now need to be given as meeting_user ids via the new field submitter_meeting_user_ids instead of how it was done before (as user ids via the field submitter_ids)
• chat_message.create now only works if the user is in the meeting
• same with personal notes

TODO:

• Write migration
• Take care of supporter after PR Implement motion_supporter model #3173 is merged
• remaining tests in migration (see todos in code)
• Write client issue for this (motion create should auto-fill submitter if possible)

[hjanott]

With this change it will be impossible to remove a user from a meeting and rejoin him with all relations to meeting user submodels set in place again because the information is lost.
In general I'm against this change unless the user_id is stored in all meeting_user related models as well. However that's also not well designed.

[hjanott]

Why is this necessary?

[hjanott]

Suggested change

	And(
	FilterOperator("user_id", "=", instance["id"]),
	FilterOperator("meeting_id", "=", removed_meeting_id),
	),
	self.get_meeting_user_filter(instance["id"]), removed_meeting_id)),

[hjanott]

Or use get_meeting_user.

[hjanott]

It would be more efficient to filter all meeting users where group_ids is empty list or None.

[hjanott]

Suggested change

	Returns the list of speaker_ids that should be deleted ad pos 0
	Returns the list of speaker_ids that should be deleted at pos 0

[hjanott]

self.countdown_change_events will always be an empty list and never be accessed by its name here. Better to create it after this function was used.

[hjanott]

See below comment.

Suggested change

and the list of events for the countdown changes for that deletion at pos 1

[hjanott]

Suggested change

	for id_, meeting_user in models_to_delete.items():
	for field, value in meeting_user.items():
	for id_, model in models_to_delete.items():
	for field, value in model.items():

[hjanott]

Suggested change

	if field_data := COLLECTION_TO_MIGRATION_FIELDS[collection].get(field):
	if is_list_field(field) and value:
	for val_id in value:
	self.handle_id(collection, id_, val_id, field, field_data)
	elif value:
	self.handle_id(collection, id_, value, field, field_data)
	if field_data := COLLECTION_TO_MIGRATION_FIELDS[collection].get(field) and value:
	if is_list_field(field):
	for val_id in value:
	self.handle_id(collection, id_, val_id, field, field_data)
	else:
	self.handle_id(collection, id_, value, field, field_data)

[Elblinator]

If a participant is allowed to create motions/amendments but cannot manage motions/ meta data the backend is stopping the participant from creating the motion/amenment:

Motion:

{
  "action": "motion.create",
  "data": [
    {
      "meeting_id": 1,
      "title": "we",
      "text": "<p>e</p>",
      "submitter_meeting_user_ids": [
        2
      ],
      "workflow_id": 1
    }
  ]
}

Response:

{
    "success": false,
    "message": "You are not allowed to perform action motion.create. Forbidden fields: submitter_meeting_user_ids with possibly needed permission(s): motion.can_manage, motion.can_manage_metadata"
}

Amendment:

payload: 
{
  "action": "motion.create",
  "data": [
    {
      "meeting_id": 1,
      "lead_motion_id": 11,
      "title": "Änderungsantrag zu 01",
      "submitter_meeting_user_ids": [
        2
      ],
      "workflow_id": 1,
      "reason": "",
      "amendment_paragraphs": {
        "0": "<p>s gxd.kui hg bvear ertg</p>"
      }
    }
  ]
}

response:

{
    "success": false,
    "message": "You are not allowed to perform action motion.create. Forbidden fields: submitter_meeting_user_ids with possibly needed permission(s): motion.can_manage, motion.can_manage_metadata"
}