[Easy]: Remove debug console logs from production UI paths

### Problem Statement

Normal user flows log too much debug output, making browser console noisy and harder to debug real issues.

### Files and Scope

event-dappp/src/App.js
event-dappp/src/components/UserProfile.jsx
event-dappp/src/components/EventList.jsx

### Acceptance Criteria

- [ ] Non-essential console logs are removed or guarded behind development-only checks
- [ ] Error logs for real failures remain meaningful
- [ ] Login, profile, and ticket purchase flow behavior remains unchanged
- [ ] Frontend build succeeds after cleanup

### Test Plan

Run app and perform login, ticket browse, and profile actions.
Check browser console for reduced noise.
Trigger one controlled error and confirm useful error log remains.

Inspect event-dappp/src/App.js, event-dappp/src/components/UserProfile.jsx, and event-dappp/src/components/EventList.jsx for non-essential console logs and existing error logging. Run the frontend build, then exercise login, ticket browsing, and profile flows while checking that the console is quieter and controlled errors still produce useful logs.

Written by the indexing model from the issue text.