Allow the orgaadmin to do more

[luisa-beerboom]

Closes #2737
Also allow cloning and deleting of locked meetings as long as the caller has settings manage perms in that meeting

[hjanott]

LGTM. I added some suggestions of which some repeat in other places of the code.

[MSoeb]

Found some permission issue: All is tested as Orgaadmin which is not part of a committee or meeting.

• Committee menu: Create a meeting is not possible. Orgaadmin needs to be committee admin to create a committee. Following the superadmin permissions, this should be possible without setting the orgaadmin as committee admin.
  

• Committe menu > meeting edit: Edit is not possible. Wanted behavior: Same as above.
  

• Meeting > Participants > Add or edit a user: Adding or editing a participant doesn't work. Permission is missing. Wanted behavior: Should work, without being a part (admin) of the meeting.
  

• Motions > create a motion: Didn't work if the submitter is a new participant. This is a follow up of the previous point. I assume, that this behavior will happen on every action that requires to add or edit a participant. Wanted behavior: Creating a motionwithout being part of the meeting should be possible. Just like superadmins can do it.
  

• Meeting > Autopilot: If something is projected, that provides the possibility to create a point of order, this action doesn't work. An error appears, because the orgaadmin is not part of the meeting. -> Creating a point of order should be possible, just like it is for a superadmin.
  

[luisa-beerboom]

I'll preface this by saying: If you want backend development to run efficiently please provide payloads if something's not working. Otherwise the bugs may be hard to replicate.

Also: From the fact that I couldn't even replicate the easy-to-understand ones, I wonder if maybe you tested with the wrong backend version.

Found some permission issue: All is tested as Orgaadmin which is not part of a committee or meeting.

* Committee menu: Create a meeting is not possible. Orgaadmin needs to be committee admin to create a committee. Following the superadmin permissions, this should be possible without setting the orgaadmin as committee admin.

Couldn't replicate.

* Committe menu > meeting edit: Edit is not possible. Wanted behavior: Same as above.

There's some fields that shouldn't be working, like the jitsi fields, however I can't tell if they're the ones causing problems for you. Please tell me what fields are causing problems specifically (maybe using the action documentation for meeting.update as a guideline) and please provide a payload anyway.

* Meeting > Participants > Add or edit a user: Adding or editing a participant doesn't work. Permission is missing. Wanted behavior: Should work, without being a part (admin) of the meeting.

Couldn't replicate, neither with user.create nor user.update.

* Motions > create a motion: Didn't work if the submitter is a new participant. This is a follow up of the previous point. I assume, that this behavior will happen on every action that requires to add or edit a participant. Wanted behavior: Creating a motionwithout being part of the meeting should be possible. Just like superadmins can do it.

As far as I know the client adds the new user separately. Since there are two actions involved, I can't even tell if this is actually a backend problem, or if the client is doing something wrong.

* Meeting > Autopilot: If something is projected, that provides the possibility to create a point of order, this action doesn't work. An error appears, because the orgaadmin is not part of the meeting. -> Creating a point of order should be possible, just like it is for a superadmin.

I don't fully grasp what situation you are talking about, since projection dont' have points of order. Also the snackbar message is clearly a client-side error. While this may just be a chain reaction thing caused by a backend error, I really can't tell what the error would actually be, so please provide more information