Rework content scopes management in the user permissions panel

[fraxachun]

Problem

The user permissions panel derived its content scope columns from the data of each individual user, so the set of columns was inconsistent between users and dimensions without a value (e.g. a wildcard dimension or an optional dimension not part of availableContentScopes) were not shown at all. Assigning content scopes did not support wildcard/free-value dimensions, and the assigned-scopes and permission-specific-scopes UIs were separate implementations.

Solution

Render a consistent set of content scope columns for every user based on the content scope dimensions declared in the API (userPermissionsAvailableContentScopeDimensions). A dimension whose value is the "*" wildcard is shown as "All".

• Content scopes are assigned through an "Add scope" dialog that builds a scope from one dropdown per enumerable dimension, cascading so that only existing combinations can be selected. Dimensions that are not part of availableContentScopes are entered as a free text value (* grants all values).
• The assigned content scopes and the permission-specific content scopes (override dialog) share the same paginated grid and add dialog, and show manually assigned scopes first.
• Removing a content scope asks for confirmation, consistent with removing a permission, and the assignment type is presented consistently across the permissions and content scopes grids.
• The userPermissionsContentScopes query now returns the user's content scopes as-is instead of intersecting them with availableContentScopes, so wildcard and other free content scopes are shown in the assigned-scopes grid.

Screenshots/screencasts

To be added.

Stacked pull request

This is layer 4 of 4 of a stacked pull request. Review and merge bottom-up (each layer targets the one above it):

1. Support wildcard values for content scope dimensions → main (Support wildcard values for content scope dimensions #6114)
2. Summarize a user's content scopes per dimension in the users list → Support wildcard values for content scope dimensions #6114 (Remove the Permissions and Scopes columns from the user permissions users list #6135)
3. Allow declaring content scope dimensions at runtime → Remove the Permissions and Scopes columns from the user permissions users list #6135 (Allow declaring content scope dimensions at runtime #6115)
4. Rework content scopes management in the user permissions panel (this PR) → Allow declaring content scope dimensions at runtime #6115 (Rework content scopes management in the user permissions panel #6116)

Replaces #5985, which combined all layers.

🤖 Generated with Claude Code