Display only warnings of the currently selected scope by default

[raphaelblum]

Description

The warnings overview and the "Latest Warnings" dashboard widget query the warnings of every scope the user may access. For an admin that is every scope in the project, which makes the list hard to read — the ticket asks for the warnings of the current scope instead, without the user having to set a filter by hand.

WarningsGrid and LatestWarningsDashboardWidget now pass the current content scope as the scopes query variable instead of all allowed scopes. Switching the scope updates the list, because the query variable changes.

Warnings that have no scope at all (DAM warnings, for instance) or only a part of a scope (only domain) stay visible. The resolver already adds the partial scopes to the query and always matches scope IS NULL next to the requested scopes, so this needs no API change.

WarningsPage also passes showAllScopes to its ContentScopeIndicator, so the page shows the current scope instead of "Global" unless all scopes are requested.

Example

The new default needs no configuration. To keep the previous behavior, set the new showAllScopes prop:

<WarningsPage showAllScopes />

<LatestWarningsDashboardWidget showAllScopes />

Acceptance criteria

• I have verified if my change requires an example
• I have verified if my change requires a changeset
• I have verified if my change requires screenshots/screencasts

Screenshots/screencasts

Before	After
Link	Link

Open TODOs/questions

• Add before/after screenshots of the warnings grid and the dashboard widget
• This changes the default for existing projects: after the update they show fewer warnings than before, without a code change on their side. I consider that acceptable, because the previous default is what the ticket reports as the problem, and showAllScopes restores it in one line. If someone sees it differently, I can turn the prop around — keep all scopes as the default, let projects opt in to the current scope — and change the default in the next major instead.

Further information

• Task: https://vivid-planet.atlassian.net/browse/PHSB2C-11865
• The approach follows the discussion in the ticket: set the scopes query variable in the admin rather than adding a second grid or a project-specific one.