Add the missing maxQuotaScopeSize and keypair user filters to the Resource Policy V2 lists

Page: /admin/resource-policy. Source: report-resource-policy.md.

- User and Project tabs: add a `maxQuotaScopeSize` filter (server IntFilter in bytes; the column shows a humanized size, so the filter input must accept a size with unit and convert to bytes).
- Keypair tab: add `keypair.userId` filter (user select). Added in 26.4.4 but the V2 tab only renders on >=26.7.0, so no extra gate is needed.
- `maxPriority` (26.8.0) is out of scope until data/schema.graphql is re-synced.

JIRA Issue: FR-3912

Start at the /admin/resource-policy page and use report-resource-policy.md to locate the User, Project, and Keypair tab filter definitions. Add the maxQuotaScopeSize filters with size-to-byte input handling and the keypair.userId user select; verify both filters render and work, while leaving maxPriority out of scope.

Written by the indexing model from the issue text.