FIX: add privy env vars

[pedroanastacio]

Description

• Add Privy env vars

Checklist

• I reviewed my PR code before submitting
• I ensured that the implementation is working correctly and did not impact other parts of the app
• I implemented error handling for all actions/requests and verified how they will be displayed in the UI (or there was no error handling needed).
• I mentioned the PR link in the task

[guimroque]

🔴 CRITICAL: Sensitive credentials committed to repository

Problem: You're committing Privy App ID and Client ID directly to the repository. This violates our security standards which explicitly state "Nunca commitar: .env, tokens, secrets, credentials". These values will be visible in git history and accessible to anyone with repository access.

Suggestion:

1. Remove these values from the commit
2. Add them to your local .env.production file (which should be gitignored)
3. Document the required environment variables in README or a .env.example file
4. Use your deployment platform's environment variable configuration to set these in production

[guimroque]

Code Review

Summary

This PR adds Privy environment variables to the production configuration. However, it commits sensitive credentials directly to the repository, which is a critical security violation according to our standards.

Strengths

• Clear and focused change addressing Privy configuration
• Proper file targeting for production environment

Issues

• 1 critical security issue that blocks merge