[Web] Respect Max Quota in Quota Selection

[exalate-issue-sync]

Description

User Stories

• As an organisation who needs to economize Storage, I want to nudge users to set low quotas but still want to provide the freedom to set maximum quota if really needed.

Value

• enforce max quota value
• save quota
• tempt users to economize storage
• provide freedom to use max quota if really needed

Acceptance Criteria

• Max Quota value is respected: User can not enter a higher value than the max quota value
• If a higher quota than max quota is entered, a validation error is shown:
  • "Please enter a value less than [maxQuota] GB."
• Predefined items in drop menu are:
  • 1 GB
  • 2 GB
  • 5 GB
  • 10 GB
  • 50 GB
  • 100 GB
• If the max quota value is less than 100 GB, predefined Items bigger than the max value are cut off / not shown. (ex. Max Quota is "40 GB", predefined items are: 1,2,5,10 GB)
• Make sure, that the described behaviour is applied to existing quota selection components in Administraion Settings (if existent):
  • Users (Edit)
  • Spaces (Edit Quota)
• If there is no maxQuota value defined in the graph API, then offer the option "unrestricted" in the drop menu.

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