Multi-Domain-Asset-Infrastruktur: geteilte Vite-Konfiguration und DomainAssetContext

- vite.shared.js als gemeinsame Quelle fuer Ports, Hot-Files, HMR-Hosts
  und CORS-Origins der beiden Vite-Builds (Portal/Web)
- App\Support\DomainAssetContext kapselt die Vite-Build-Directory-
  Konfiguration pro Domain (ThemeServiceProvider + Auth-Layout nutzen ihn)
- Tailwind-Portal-Content-Globs auf die tatsaechliche View-Struktur gezogen
- Dev-Beispiel-Routen + Tests (DomainAssetContextTest, DevExampleRoutesTest)
- Aufraeumen: versehentliche Leerdatei dev:web entfernt

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

routes/web.php

@@ -6,6 +6,7 @@ use App\Http\Controllers\PressReleasePreviewController;
 use App\Models\Category;
 use App\Models\Company;
 use App\Models\PressRelease;
+use App\Support\DomainAssetContext;
 use Illuminate\Database\Eloquent\Builder;
 use Illuminate\Support\Carbon;
 use Illuminate\Support\Facades\Route;
@@ -33,7 +34,9 @@ $applyWebDomainConfig = static function (string $domainKey): array {
     View::share('domainName', $domainConfig['domain_name'] ?? request()->getHost());
     View::share('domainConfig', $domainConfig);
     View::share('domainUrl', $domainConfig['url'] ?? config('app.url'));
-    View::share('assetUrl', $domainConfig['url'] ?? config('app.url'));
+    View::share('assetUrl', DomainAssetContext::staticAssetOrigin($domainConfig));
+
+    DomainAssetContext::configureVite($domainConfig);
 
     return $domainConfig;
 };