fix: personal access tokens failed with a 500 in production

Passport needs a "personal access client" to issue personal access tokens,
and only the seeder created it (production runs migrations, not the seeder),
so createToken threw "Personal access client not found".

- New idempotent command passport:ensure-personal-client, run by the
  container entrypoint after the migrations.
- The tokens page now shows an error when the server fails instead of
  doing nothing (es, en, ca).
- Tests: the command creates the client once; tokens can be created.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

resources/js/i18n/ca.ts

@@ -23,6 +23,7 @@ const ca: MessageSchema = {
         edit: 'Editar',
         delete: 'Esborrar',
         none: '(cap)',
+        unexpectedError: "Alguna cosa ha fallat. Torna-ho a provar d'aquí a una estona.",
     },
     login: {
         title: 'Entrar',

resources/js/i18n/en.ts

@@ -23,6 +23,7 @@ const en: MessageSchema = {
         edit: 'Edit',
         delete: 'Delete',
         none: '(none)',
+        unexpectedError: 'Something went wrong. Please try again in a moment.',
     },
     login: {
         title: 'Sign in',

resources/js/i18n/es.ts

@@ -21,6 +21,7 @@ const es = {
         edit: 'Editar',
         delete: 'Borrar',
         none: '(ninguno)',
+        unexpectedError: 'Algo salió mal. Probá de nuevo en un momento.',
     },
     login: {
         title: 'Ingresar',