Add Admin Edit Profile with MFA, locale & currency; i18n and infra UI improvements

[gerichkoeke]

Motivation

• Provide a full-featured admin profile page with MFA support and user-selectable language and currency, and ensure locale/currency persist and apply across panels.
• Improve customer infrastructure pages with translated labels, dark-theme fixes and actions to remove network configuration.
• Synchronize locale/currency changes for Distributor and Partner users into their related models and the active session to keep UI consistent.

Description

• Added a new admin profile page App\Filament\Admin\Pages\Auth\EditProfile with MFA setup/confirm/disable methods, a two-form layout (profile + MFA), locale and currency selects, and a corresponding Blade view at resources/views/filament/admin/pages/auth/edit-profile.blade.php, and registered it in AdminPanelProvider via ->profile(...) with isSimple: false.
• Extended Distributor and Partner profile pages to save locale and currency to their associated distributor/partner models, call syncLocaleToProfile(...), and set the session and app() locale after update, plus added the language/currency selects into the forms.
• Updated Customer resource pages (admin and partner) and many Blade templates to replace hard-coded strings with translation keys from lang/*/app.php, add UI/dark-mode styling improvements, add network deletion UI and actions, add proposal/generate labels, and wire new translations like app.customer_infra.*.
• Changed network-delete logic in CustomerInfra pages to clear firewall_option_id and lan_to_lan_address and added the new fields to Project model (extra_public_ips, extra_ip_price, network_configured, lan_to_lan_address) and casts for network_configured.
• Updated DistributorPanelProvider to use the distributor-scoped EditProfile page class and adjusted user menu labels to use translation keys.

Testing

• Ran the Laravel test suite with php artisan test and vendor/bin/phpunit and the existing automated tests completed successfully.
• Verified there were no failing PHP syntax errors or obvious runtime errors when loading the modified Filament pages in a development environment.

---

Codex Task