Fix LDAP login: ensure password encoding and include user in response

- Fix password encoding: Convert password to UTF-8 bytes for LDAP protocol compatibility
- Add 'user' field to TokenResponse schema for frontend compatibility
- Update login endpoint to populate user object in response
- Resolves 'Invalid Protocol Password' error on LDAP login attempts

The issue was that frontend expected response.user but backend only returned
individual fields (user_id, username, role), causing localStorage assignment to fail.

.standalone.pid

@@ -1,3 +1,3 @@
-65062
-65063
-65079
+98497
+98498
+98515