Feat 99 setup wizard

[mohammadsherif0]

Main Description

This branch delivers a guided onboarding experience for CARE by introducing a first-time setup wizard and aligning the admin Settings UI to the same structure and language.
It addresses the original problem that setup was fragmented, technical, and hard to follow by having a clear step flow (admin creation, general, mail, registration, moodle, summary).

#99

New User Features

• First-time setup wizard flow with ordered steps for admin account creation and system configuration.
• Summary step before finish so admins can review all selected values in one place.
• Import settings from previous instance inside the wizard via JSON.
• Download current settings snapshot as JSON to reuse across deployments.
• Built-in test mail action during setup so admins can verify mail settings before finishing setup.
• Mail setting updates apply directly from Dashboard Save Settings (no backend restart required).
• Clearer setting labels/grouping for better readability compared to technical/raw key names.

New Dev Features

• Local dev workflow target split (make dev vs make dev-wizard) to simplify testing both default paths.
• Setup mail test capability wired into the setup flow, making mail configuration easier to validate during development and QA.
• Mail service settings now refresh without manual backend restart, reducing friction during iterative config/testing.

Improvements

• Simpler first-time user experience by replacing scattered dashboard configuration with one guided setup path.
• Faster initial setup completion through step-by-step flow and in-wizard review.
• Settings page rework toward wizard-like structure, improving consistency between first-time setup and ongoing configuration.
• Better subsection ordering and grouping in settings/wizard views.
• Operational UX improvement for mail configuration: changing mail settings and saving in dashboard is enough; no backend refresh workflow needed.

[dennis-zyska]

I'm not sure if this is the correct way to do it. It is really hard to get an overview and there is a huge list of props in the components. The usual way to do is, to reduce props and use computed also within each subcomponent. That guarantees a better overview, that is also why we have the vuex store