chore: add no-console ESLint rule to prevent debug statements in production

[Aarti-panchal01]

📋 Description

Adds no-console ESLint rule to automatically catch console statements
in future code. Complements the console cleanup in PR #344.

Related to PSMRI/AMRIT#130 (C4GT DMP 2026)

✅ Type of Change

• ⚙️ Config change
• 🧹 Chore

ℹ️ Additional Information

Rule: "no-console": ["error", { "allow": ["warn", "error"] }]
Any future console.log will now fail the ESLint check automatically.

[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

[coderabbitai]

Warning

Rate limit exceeded

@Aarti-panchal01 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 47 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: e33f2389-6f73-4296-a053-e29d6983112c

📥 Commits

Reviewing files that changed from the base of the PR and between 91045e5 and 2d48b41.

📒 Files selected for processing (1)

• .eslintrc.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Aarti-panchal01]

Hi @drtechie,

Added the no-console ESLint rule as a follow-up to the console cleanup in PR #344.

This ensures future contributors to MMU-UI can't accidentally commit console.log statements — the linter will catch it automatically.
Especially useful during the Angular 16→19 migration when new components will be written from scratch.

This way we don't need to manually hunt console statements in code reviews.