Motion detail view: Add new UI element - session sequence - for motion forwarding

[MSoeb]

Current behavior
Currently it is only possible to see a limited path of motion forwarding. It is not possible to see the whole path. It is restricted. This limits the usefullness of the motion forwarding.

Wanted behavior

• A motion session sequence should be integrated into the motion detail view, which displays all forwarding steps of a motion in the order they occurred as a simple path model. This enables the traceability and tracking of motions.
• Each forwarding step is displayed with the meeting title and current motion state. The visibilty of the state should limited by the workflow restriction of the meeting of the motion. (Example: If there is a restriction set to the motion submitter, the motion sequence should not display it.)
• In addition, motion metadata (location and date) is visible via tooltips .
• If accounts have access to a meeting, the meeting titles can be used as links to the meeting; excactly to the motion.
• If a motion in the path is in a closed meeting, the path should show this meeting as '[Lock-Icon] Closed Meeting' without a tooltip.
• Based on the point before: If a user has access to the closed meeting, the real name of the meeting with tooltip should be shown. The motion status should be visible for the user according to the visibility permission he has inside the closed meeting.
• This feature can be enabled via a motion setting.

See the mockup for details.

Mockup-Beratungsfolge_20260428.pdf

[peb-adr]

A thought voiced by @ostcar:
It should be considered that some motions may not be visible to some users.
Implementing this should not introduce a way to somehow access motions or meta info that should not be visible to that specific end user.

This would mean that depending on view permissions the chain would become apparently shorter (omitting non-allowed motions).

[peb-adr]

Adding the new setting for this, would also call for a migration, which is currently not supported - waiting for the DaMMi project. One solution would be to implement the feature first and adding the setting for enabling/disabling it at a later point.

[MSoeb]

Note: Iv'e added some new requirements for closed meetings. Please take care of them.