Add rule "Optimize browserlist tag in package.json"

[utarwyn]

It might be interesting to start with the idea given by a group of spotters at the 2023 hackathon:
green-code-initiative/creedengo-challenge#54

[Geenag]

Team TERRE take this one

[utarwyn]

Just for clarity 🤞

This rule is feasible, but only as a SonarQube-specific rule — not for the standalone ESLint plugin. Here's why:

• ESLint rules operate per-file and have no standard way to access project-level config files
• Rules would report the warning 50+ times (once per JS file in the project) → poor UX
• No reliable path resolution for package.json across different project structures
• Sandboxed environments (online editors, CI with restricted permissions) have no file system access

Why SonarQube works:

• ✅ SonarQube Sensors have guaranteed file system access
• ✅ Can read package.json and .browserslistrc reliably
• ✅ Reports single project-level issue (not spam)
• ✅ Integrates with SonarQube dashboard

---

Warning

This rule would be implemented in Java in the SonarQube plugin, not JavaScript for the ESLint plugin.

Resources

• SonarQube Custom Rules Documentation
• SonarQube Java Language Documentation
• Browserslist Documentation

[fatenhomrani]

@sebastien Meynet