Add Topic queue configuration portfolio

## Problem

The Topic page lists queue counts and permissions per row, but operators cannot see configuration fragmentation or capacity distribution across a full instance. Because the table is paginated, asymmetric queues, restricted permissions, and one-off profiles are difficult to identify at fleet scale.

## Proposed change

Add an on-demand queue configuration portfolio that:

- loads all topics matching the current instance and filters through the existing bounded pagination helper;
- groups topics by type, namespace, write/read queues, and permission;
- classifies balanced, asymmetric, read-only, write-only, no-access, and unknown-permission profiles;
- aggregates queue capacity, message volume, TPS, consumers, profile share, and representative topics;
- supports status filtering and search;
- includes focused tests and Chinese/English UI copy.

This is a read-only analysis over existing Topic metadata and introduces no backend contract.

Start at the Topic page and trace the existing bounded pagination helper used for instance and filter queries. Define the portfolio around the listed grouping, profile classifications, aggregates, status filtering, search, focused tests, and Chinese/English copy; it is done when the read-only view covers all matching topics without a backend contract change.

Written by the indexing model from the issue text.