[web] Privacy statement in account menu (authenticated)

[exalate-issue-sync]

Description

User Stories

• As a Compliance Manager I want to link to the privacy and imprint pages for loged in users so that ocis is compliant.

Value

compliance

Acceptance Criteria

• add 2 config options in theme.json (precedence) and web config file (fallbackl) to link to privacy & imprint pages (Default: empty)
  • if the values are set in theme.json, this value takes precedence
  • if there are no values set in theme.json, the web config value is used as a fallback
  • Note: reasoning for this double-config is to be prepared for the later implementation for ownbrander & theme.json; also currently the theme.json gets all-or-nothing evaluated which needs some refactoring later.
  • labels for "Imprint" and "Privacy" are hardcoded and need to be translated.
• If one or both options are set, the corresponding links are shown in the account menu
• first iteration: applies only to authenticated users (because the menu is not shown in unauthenticated state)
• Not part of this story: legal links for unauthenticated users

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
  [ ] automated tests passed (if automated tests are not available, this test needs to be created and passed
• Non-functional requirements
  [ ] no sonar cloud issues