[FIX] ServicesController + simulate-nis2: adatta a schema users reale (full_name, is_active)

- ServicesController::provision(): INSERT users usa full_name/is_active (non first_name/last_name/status)
- ServicesController::ssoLogin(): stesso fix per SSO user creation
- simulate-nis2::ensureUser(): registration payload usa full_name (non first_name+last_name)

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

simulate-nis2.php

@@ -196,19 +196,17 @@ function ensureUser(string $firstName, string $lastName, string $email, string $
 
     // Registrazione
     $regRes = api('POST', '/auth/register', [
-        'first_name' => $firstName,
-        'last_name'  => $lastName,
-        'email'      => DEMO_EMAIL !== $email ? DEMO_EMAIL : $email,
-        'password'   => $password,
-        'role'       => $role,
+        'full_name' => trim("$firstName $lastName"),
+        'email'     => DEMO_EMAIL !== $email ? DEMO_EMAIL : $email,
+        'password'  => $password,
+        'role'      => $role,
     ]);
     // Override email per demo (sempre DEMO_EMAIL ma tracking per slug)
     $regRes2 = api('POST', '/auth/register', [
-        'first_name' => $firstName,
-        'last_name'  => $lastName,
-        'email'      => $email,
-        'password'   => $password,
-        'role'       => $role,
+        'full_name' => trim("$firstName $lastName"),
+        'email'     => $email,
+        'password'  => $password,
+        'role'      => $role,
     ]);
     if (!empty($regRes2['data']['access_token'])) {
         $jwt = $regRes2['data']['access_token'];