fix: move inline comments above env vars in .env.local.example

[tturnerdev]

Summary

• Inline comments after = in .env files are parsed as part of the value by most env parsers (python-dotenv, shell source, etc.)
• This caused EMAIL_SMTP_USER to resolve to # Mailpit doesn't require auth, leave empty for dev instead of an empty string
• The truthy value triggered smtp.login() against Mailpit, which doesn't support SMTP AUTH without TLS, resulting in: EmailConnectionError: SMTP connection error: The SMTP AUTH extension is not supported by this server
• Moved all inline comments in the email configuration section to the line above their respective variables

Test plan

• Copy .env.local.example to .env
• Start the app with Mailpit running
• Trigger an email (e.g., team invitation)
• Verify email is sent successfully without SMTP AUTH errors

🤖 Generated with Claude Code

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[tturnerdev]

PR made with help of AI; fully reviewed and verified by me.

Some additional details:

• Issue resulted from env file copied directly from .env.local.example

Application environment details:

• App running in python venv, using VITE_DEV_MODE=true, and launching with uv run app run
• Supporting infra is running via default, provided Docker image

Otherwise, fully stock set up. The SMTP errors began immediately after adding EMAIL_BACKEND=smtp.

Before this, emails were not working at all and I had to copy the sign-up URL token directly from the logs (or edit the user in db to set to "verified").

After this change, I now see outgoing emails in Mailpit as expected.