Fix user editing and email field consistency across the platform

Update handleEditUser to prioritize firstName/lastName over the name field for user editing, and make the email field consistently optional in both create and edit forms.

Replit-Commit-Author: Agent
Replit-Commit-Session-Id: a8a78c07-e900-425c-a577-5b4c5894379d
Replit-Commit-Checkpoint-Type: full_checkpoint
Replit-Commit-Screenshot-Url: https://storage.googleapis.com/screenshot-production-us-central1/1957c339-2757-4d1f-8e92-e9f71a1ce58e/a8a78c07-e900-425c-a577-5b4c5894379d/vetH0Gp

replit.md

@@ -100,4 +100,18 @@ Preferred communication style: Simple, everyday language.
   - Removed required validation from edit form firstName/lastName fields
   - Updated placeholders to indicate "(optionnel)" for consistency
   - Maintained database schema where name fields are already optional
-- **Result**: Name fields now consistently optional across all user management interfaces
+- **Result**: Name fields now consistently optional across all user management interfaces
+
+#### User Edit Form Initialization Fix
+- **Issue**: Prénom/nom fields in edit form were not editable because they were initialized from wrong data source
+- **Root Cause**: handleEditUser was only using the `name` field instead of `firstName`/`lastName` fields from database
+- **Solution Implemented**:
+  - Modified handleEditUser to prioritize `firstName`/`lastName` fields from database
+  - Added fallback to split `name` field if firstName/lastName are empty  
+  - Fixed edit form initialization to use actual database values
+- **Result**: Edit form now properly loads existing firstName/lastName values and allows editing
+
+#### Email Field Consistency in Edit Form
+- **Issue**: Email field was marked as required in edit form but optional in create form
+- **Solution**: Removed `required` attribute and asterisk from email field in edit form
+- **Result**: Email field now consistently optional in both create and edit forms