Map MudBlazor Features/Components to Radzen Equivalents and Migration Guidance

## Goal
Establish a reference mapping of all MudBlazor components, services, and theming features in use to their closest Radzen Blazor equivalents or patterns. Document any gaps, required custom implementations, and key differences developers should be aware of when rewriting UI code.

### Tasks
- Produce a mapping table of MudBlazor component/tag → Radzen component/tag (focus: `MudButton`, `MudGrid`, `MudTable`, `MudDialog`, `MudPopover`, `MudSnackbar`, layout primitives...)
- Document theming differences (themes, palette APIs, icons, etc.) and where in the codebase theme setup occurs (see audit issue for paths: layouts, wrappers, host pages)
- Note differences in table/grid, dialog, snackbar, menu/nav, icon usage, etc. (with select code examples from layouts/shared components)
- Highlight areas needing custom work (features not supported or requiring extra effort in Radzen)
- Guidance for setting up Radzen Blazor theming/styles for consistency.

#### Deliverables
- Mapping matrix with links to target files/components
- Guidance document for the migration team
- Examples where possible, including code paths (see audit issue checklist)

**Use links to layouts, shared modules, and themes from the audit issue for reference.**

Start with the audit issue checklist and locate the referenced layouts, wrappers, host pages, shared modules, and themes. Inventory the MudBlazor components, services, and theming features found there, then produce the mapping matrix, migration guidance, examples, and a list of gaps or custom work needed for Radzen.

Written by the indexing model from the issue text.