Add ApiRequestLog observability stack and migrate User to UUID PK

[edimossilva]

Summary

Backports the request-logging middleware, admin observability dashboards, and generic User improvements (UUID PK, name column) from the plantao backend into this boilerplate. Plantao-specific business code (medical_shifts, locations, chat_messages, domain_events, app_versions, doctor/accountant roles, Firebase auth, paying flag, mobile_platform, etc.) is intentionally not brought over. Existing boilerplate features (GraphQL, Chewy, Schools, HandleFile, demo_pack, oauth pack) are untouched.

What's added

• Migrations (8): enable pgcrypto, convert users.id and devise_api_tokens to UUID, change versions.item_id to string for PaperTrail compatibility with UUID records, add name to users, create api_request_logs (with deleted_at + response_code).
• ApiRequestLog model with summary helper; User gains has_many :api_request_logs.
• ApiRequestLoggerMiddleware records every /api/* request to api_request_logs and resolves the user via the Bearer access token.
• Admin dashboards under /admin — Administrate CRUD for ApiRequestLog plus six custom dashboards: Daily Overview, Requests Dashboard, Non-2xx API Logs, User Analytics, User Lookup, Request Logs by Payload. Dashboards that originally referenced removed plantao entities have been adapted to track only User and ApiRequestLog data.
• Routes: new admin resources for the seven dashboards above.
• Specs: factory + middleware spec + six admin request specs (99 examples, 0 failures), conforming to this repo's stricter RuboCop config.
• CLAUDE.md: short note on the new middleware + dashboards.

Heads-up: UUID migration is destructive

Migrating users from bigint to UUID truncates devise_api_tokens (existing tokens become invalid) and versions (PaperTrail history is cleared). Any deployment with real data on a fork of this branch will need a coordinated re-auth + acceptance of the lost audit trail.

Test plan

• bin/rails db:drop db:create db:migrate runs cleanly; db/schema.rb shows users.id, devise_api_tokens.id + resource_owner_id, versions.id as UUID and versions.item_id as string.
• bundle exec bin/rspec -P './*/**/*_spec.rb' passes without any new regressions.
• bundle exec rubocop reports no new offenses.
• Manual smoke: create a user via POST /api/v1/users, sign in via POST /api/v1/tokens, hit GET /api/v1/users with the bearer token, and confirm a corresponding row appears in api_request_logs.
• Sign in to /admin as admin@email.com / password (after bin/rails db:seed) and click through every nav entry — each dashboard should render without errors.
• Hit /api/v1/users without a token and verify the resulting 401 shows up under /admin/api_error_logs.

🤖 Generated with Claude Code