[Web] expiration for space members

[exalate-issue-sync]

Description

User Stories

• As a teacher I want to give parents access to the Photos space of the last school trip, but limit it with an expiration date, so that the pictures are not exposed longer than strictly necessary.

Value

Acceptance Criteria

• when creating a user- or group-membership in a project space, an expiration can be selected and is used in the request which invites the new member backend side.
• when looking at an existing user- or group-membership in a project space, an expiration can be set or overwritten.
• when looking at an existing user- or group-membership in a project space, an expiration can be removed.

Definition of ready

[ ] everybody needs to understand the value written in the user story
[ ] acceptance criteria has to be defined
[ ] all dependencies of the user story need to be identified
[ ] feature should be seen from an end user perspective
[ ] user story has to be estimated
[ ] story points need to be less then 20

Definition of done

• Functional requirements
  [ ] functionality described in the user story works
  [ ] acceptance criteria are fulfilled
• Quality
  [ ] code review happened
  [ ] CI is green
  [ ] critical code received unit tests by the developer
  [ ] inviting a user to a space with an expiration and checking that the membership has been created with an expiration date has a positive e2e test (happy path). should be a dedicated e2e smoke test, not integrated into an existing test.
  [ ] automated tests passed (if automated tests are not available, this test needs to be created and passed
• Non-functional requirements
  [ ] no sonar cloud issues

[JammingBen]

Fixed via #8320.