Add tag_ids and agenda_type to agenda item duplication

[luisa-beerboom]

Closes #2496

[jsangmeister]

Well, we either restructure the client to use topic tags as well as agenda item tags or we change the backend to be able to set the agenda item tags directly, analogous to the other agenda item properties in https://github.com/OpenSlides/OpenSlides/wiki/topic.create#payload. Sooo the latter :D

The suggestion would then be to rename the tag_ids payload field to agenda_item_tag_ids and transfer these to the agenda item instead of the topic.

Furthermore, if the topic tags are not used at all, we could go ahead and remove them completely from the models.yml. I don't see any further ramifications in that if they are not used anywhere.

[luisa-beerboom]

Well, we either restructure the client to use topic tags as well as agenda item tags or we change the backend to be able to set the agenda item tags directly, analogous to the other agenda item properties in https://github.com/OpenSlides/OpenSlides/wiki/topic.create#payload. Sooo the latter :D

The suggestion would then be to rename the tag_ids payload field to agenda_item_tag_ids and transfer these to the agenda item instead of the topic.

Furthermore, if the topic tags are not used at all, we could go ahead and remove them completely from the models.yml. I don't see any further ramifications in that if they are not used anywhere.

Sounds good to me

[jsangmeister]

Opened OpenSlides/openslides-backend#1824 for this

[jsangmeister]

OpenSlides/openslides-backend#1832 was merged and tag_ids were removed from topics alltogether, so this can be continued and the field removed in the client as well

[luisa-beerboom]

For testing:
This PR might have consequences when creating an agenda item from assignments, motions and motion block, please check if these still work.

[Elblinator]

The visibility is still not dublicated correctly.
If topic A is selected with multiselect, then the visibility is changed and then it is dublicated -> the original (and not current) visibility is dublicated.

If a tag is added to a motion the tag is not carried over to the agenda, the tags from a motion should be in the agenda as well

the states/phases from a motion/election are not carried to the agenda, which is at this time the correct behaviour because these descriptions are not tags in the tag system but descriptions of the state or phases. So at the current time that is a-okay!

[luisa-beerboom]

If a tag is added to a motion the tag is not carried over to the agenda, the tags from a motion should be in the agenda as well

Talked to @MSoeb
This was not in OS3 therefore currently this is the correct behaviour and changes concerning this would be a new feature request.
Also it would honestly require quite a bit of planning and therefore it is not currently on the table