[Epic] Transition Elsa Studio UI from MudBlazor to Radzen Blazor

## Overview
We are planning to replace MudBlazor with Radzen Blazor for the Elsa Studio UI framework. This transition involves auditing, mapping, migrating, and validating all usages of MudBlazor and its extensions, and replacing them with Radzen equivalents. The process should ensure preservation of all UX features and visual polish, and work in both Blazor Server and Wasm. All code and assets currently using MudBlazor must be updated, and thorough QA should be conducted at each stage.

## Objectives
- Remove MudBlazor and associated extensions from all projects.
- Adopt Radzen Blazor and update all layouts, components, styles, and behaviors accordingly.
- Preserve all current functionality and visual/UX polish.
- Update documentation and CI configurations as needed.

## Steps
1. Analyze and inventory all MudBlazor usages and architectural touchpoints.
2. Design a migration approach and publish guidance to the team.
3. Incrementally migrate individual components, layouts, and modules to Radzen Blazor.
4. Validate, QA, and refactor as needed. Update docs and tests.

_This epic will be the parent for all migration sub-issues. Progress and technical notes should be tracked here._