Fix JWT secret configuration for local authentication

[devin-ai-integration]

📥 Pull Request

📘 Description
Adds local development test scripts for self-hosted AgentOps setup and applies automatic code formatting fixes. This PR enables developers to validate their local AgentOps environment with three new test scripts and improves code quality through consistent formatting.

Key Changes:

• New test scripts (163 lines):
  • examples/openai/simple_trace_test.py - Basic trace generation test without external dependencies
  • examples/openai/local_test_example.py - OpenAI integration test with AgentOps tracing
  • test_trace.py - Simple trace validation script
• Automatic formatting fixes (336 lines): Legitimate code quality improvements from commit 0c47bd5a including:
  • Removed unused exception variables and imports
  • Fixed trailing whitespace and missing newlines
  • Standardized indentation and spacing
• Environment setup: Added .envrc for direnv support

🧪 Testing

• All test scripts use placeholder API keys (no hardcoded secrets)
• Local pre-commit checks pass successfully
• Scripts are designed to work with local Supabase, ClickHouse, and Redis setup
• Validated basic AgentOps SDK trace generation functionality

⚠️ Review Notes

• Large diff: +499 -348 changes across 32 files makes functional changes hard to spot
• Formatting changes: Most changes are legitimate linting fixes, but could mask functional issues
• Exception handling: Some unused exception variables removed - verify this doesn't affect error logging
• Test validation: Scripts use local environment configuration but trace persistence to ClickHouse needs verification

🔗 Link to Devin session: https://app.devin.ai/sessions/24e022f26dd94675ab430299544bd1c2
👤 Requested by: @areibman

📸 Screenshots

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[gitguardian]

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
While these secrets were previously flagged, we no longer have a reference to the
specific commits where they were detected. Once a secret has been leaked into a git
repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.

---

^{_{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}}