Refactor Logger: Export SENSITIVE_KEYS for Reuse

[tmdeveloper007]

Summary of What Has Been Done

This PR addresses issue #8332.

See the corresponding issue for full details.

Closes #8332

Note: Please assign this PR to the tmdeveloper007 account.

[retenta-bot]

This pull request addresses issue #8332 by refactoring the logger to export SENSITIVE_KEYS for reuse. This change is expected to improve code maintainability and reduce duplication. Please note that similar past decisions, such as the renaming of overlapping themes for clarity and the documentation of null handling in APIs, highlight the importance of clear naming and documentation in our codebase. Thank you for your contribution, and feel free to reach out if you have any questions!

[github-actions]

📦 Next.js Bundle Size Report (Gzipped Sizes)

✨ No significant bundle size changes detected.

📊 Summary of Totals

Category	PR Size	Base Size	Difference
Total JS	4052.50 KB	4052.50 KB	0 B
Total CSS	338.94 KB	338.94 KB	0 B

[Aamod007]

Exporting SENSITIVE_KEYS as a typed const array for reuse — good security-aware refactoring. CI failing — please fix.

Labels: level:beginner, quality:clean, type:refactor, type:security, mentor:Aamod007

[Aamod007]

Re-reviewing after noting the only CI failure is Vercel authorization (not code-related). All other checks (Format · Lint · Typecheck · Test, Production Build, CodeQL) pass. Approving — the Vercel deploy auth is a repo-level config issue, not a code problem.