fix(auth): make request-code handler resilient to body param types

Refactors the parsing of the `isDashboardLogin` parameter in the
`/api/v1/auth/request-code` route handler.

Previously, the handler would crash with a type cast error if the
`isDashboardLogin` value was sent as a string (e.g., `"true"`) instead
of a boolean.

This change introduces robust parsing that correctly handles values
that are boolean `true`, the string `"true"`, or missing, preventing
the 500 Internal Server Error and making the endpoint more resilient
to varied client implementations.

Author: fulleni

routes/api/v1/auth/request-code.dart

@@ -43,8 +43,17 @@ Future<Response> onRequest(RequestContext context) async {
     );
   }
 
-  // Check for the optional dashboard login flag. Default to false if not present.
-  final isDashboardLogin = (body['isDashboardLogin'] as bool?) ?? false;
+  // Check for the optional dashboard login flag. This handles both boolean
+  // `true` and string `"true"` values to prevent type cast errors.
+  // It defaults to `false` if the key is missing or the value is not
+  // recognized as true.
+  final isDashboardLoginRaw = body['isDashboardLogin'];
+  var isDashboardLogin = false;
+  if (isDashboardLoginRaw is bool) {
+    isDashboardLogin = isDashboardLoginRaw;
+  } else if (isDashboardLoginRaw is String) {
+    isDashboardLogin = isDashboardLoginRaw.toLowerCase() == 'true';
+  }
 
   // Basic email format check (more robust validation can be added)
   // Using a slightly more common regex pattern