Investigate get_forwarding_meetings and motion.create_forwarded

[luisa-beerboom]

See OpenSlides/openslides-backend#2003 and OpenSlides/openslides-backend#2009

According to tracebacks in the logs it seems these two processes were called with insufficient payloads.

The get_forwarding_meetings presenter was seemingly called with a payload that didn't contain a meeting_id
The motion.create_forwarded action was seemingly called without a meeting_id and, another time, without an origin_id.
The latter action also has other required fields, but they would not have caused the same error in the backend.

Please take a good look at these actions in particular and check if the client can actually be made to send these types of payloads and, if yes, fix that

[reiterl]

The get_forwarding_meetings presenter is called in the motion-forward-dialog. The activeMeeting.meetingId could be null in some cases, so add a check here.

[reiterl]

I looked at the MotionRepositoryService.createForwarded() function. I don't find the reason, why meeting_id or origin_id could be null or undefined. Mmh, no idea. This seems to be the only function in which the CREATE_FORWARDED action is used.

[rrenkert]

#3527 and #3529 are features in same scope. Can we have this one in mind when working on them?