[Feature Request]: Support Custom/Multiple Delimiters in 'Top Namespaces' Table

Problem description (Describe the problem you would like to solve with this feature request or suggested idea).
Support for custom delimiters has been in Tree View for a bit now and it's a feature I regularly use. I'd also like that extended to Analysis view, specifically the 'Top Namespaces' section. It can be somewhat inaccurate when keys have multiple namespace delimiters. For example, for a database that uses both/ and : delimiters, the resulting table can report both XYZ/abc:* and XYZ/123:* as separate top level namespaces.

How often do you encounter this problem (Describe how frequently this problem occurs).
Frequently, when I work on monitoring usage for databases with some keys having multiple delimiters

Alternatives considered (Describe any alternative features or products you've considered).
While renaming the keys is possible, the impact and effort required is not justifiable for my cases

Additional information (Add any other context or details here).

Start by locating the Analysis view's Top Namespaces implementation and compare it with the existing Tree View custom-delimiter support. Trace how keys are grouped when both / and : are used, then define completion as the table correctly combining namespaces according to the configured delimiters and covering the reported database-key example.