Standardized logging, remove repo-wide console usage

[must108]

Background

There are multiple instances of console.log() and console.error() repo-wide. These are accompanied with eslint disable comments. Instances have been identified in #381. Logging behavior is also inconsistent in apps/packages/.

Main concerns:

• PII (personally identifiable information) can be logged in browser (bad)
• console is now an error in eslint
• inconsistent and unclear logging generally

Files with this issue are listed below:

• apps/blade/src/app/_components/admin/club/events/view-attendance-button.tsx
• apps/blade/src/app/_components/admin/club/members/member-profile.tsx
• apps/blade/src/app/_components/admin/hackathon/events/view-attendance-button.tsx
• apps/blade/src/app/_components/admin/hackathon/judge-assignment/judges-client.tsx
• apps/blade/src/app/_components/dashboard/hacker/hacker-application-form.tsx
• apps/blade/src/app/_components/dashboard/member-dashboard/download-qr-pass.tsx
• apps/blade/src/app/api/trpc/[trpc]/route.ts
• apps/club/src/app/_components/contact/contact-form.tsx
• packages/auth/src/config.ts
• packages/db/scripts/bootstrap-superadmin.ts
• packages/db/scripts/get_prod_db.ts
• packages/db/scripts/seed_devdb.ts
• packages/utils/src/logger.ts (this is a placeholder logger)

Implementation

1. Update console.log() and console.error() to the logger repo-wide
2. Remove TODO and eslint suppressions from all instances
3. Actually implement packages/utils/src/logger.ts
4. Scope decisions (could take a while):

• how and when to use .log() and .error() in the logger.
• what data should not be logged (PII for example, might involve more changes)
• how the logger should work on the client and server (to avoid leaking sensitive data)

Scope decisions are OOS for this issue and will likely be handled later, due to broader discussion on the topic.

[must108]

can be split into sub-issues as well based on complexity of tasks