The create-space quota field does not distinguish the server default from unlimited #3719

Initial Checklist

• I understand this is a bug report and questions should be posted in the Community Discussions
• I searched issues and couldn’t find anything (or linked relevant results below)

Bug Description

When creating a space, the quota field shows "No restriction", but the request omits the quota and the backend applies GRAPH_SPACES_DEFAULT_QUOTA (1 GB by default). The UI does not distinguish using the server default from explicitly requesting unlimited storage.

Reproduction Steps

1. Open Spaces → New → Options → Advanced with permission to set quotas.
2. Observe that the quota field shows "No restriction".
3. Create the space without changing the quota.
4. Inspect its quota: the configured server default has been applied.

Expected Outcome

• Offer a separate "Default" option and preselect it when creating a space.
• Selecting "Default" omits the quota so the backend applies its configured default.
• Explicitly selecting "No restriction" sends quota: { total: 0 } and creates an unlimited space.
• An explicitly selected numeric quota is sent in the create request.
• Respect the permission to set quotas and the configured maximum quota; do not offer unlimited when the maximum rules it out.

The frontend does not need to know the numeric server default to offer this behavior.

Actual Outcome

The field shows "No restriction", while the space gets quota.total = 1000000000 with the default backend configuration.

Notes

Fixed by #3728 using a separate "Default" option. Creating spaces is not blocked by exposing a default-quota capability.

Showing and selecting the configured default when editing an existing quota is a separate follow-up tracked in opencloud-eu/opencloud#3718. This needs the default value or an explicit apply-default operation; omitting the quota or sending null in an update does not currently apply the default.