fix(rome_js_analyze): accept const as non camel case

[xunilrj]

Summary

This PR fixes a false flag of all uppercase const as an invalid non-camel case.
Fixes a lot of issues here: https://github.com/rome/tools/runs/8188485278

Test Plan

> cargo test -p rome_js_analyze -- camel_case

[netlify]

✅ Deploy Preview for rometools canceled.

Name	Link
🔨 Latest commit	c939931
🔍 Latest deploy log	https://app.netlify.com/sites/rometools/deploys/631bafefae531e00080a4cc0

[github-actions]

Playground for commit d6f64ce

[ematipico]

Could you enable the rule inside rome.json file? Doing so it will be a better proof that this PR fixes the false positives

[ematipico]

Does this fix cover cases like const { FOO } = env?

[xunilrj]

Yes. I update the test with more cases.
There is one case we do not deal well.

warning[js/useCamelCase]: Prefer variables names in camel case.
   ┌─ useCamelCase.js:31:5
   │
31 │ let UPPER_CASE = 1;
   │     ----------

Safe fix: Rename this symbol to camel case
      | @@ -28,7 +28,7 @@
27 27 |   let camelCase;
28 28 |   let longCamelCase;
29 29 |   
30    | - let UPPER_CASE = 1;
   30 | + let uPPERCASE = 1;
31 31 |   let { UPPER_CASE } = 1;
32 32 |   let [ UPPER_CASE ] = 1;
33 33 |  

The problem is that it is easy to fix this, but break other acronyms like IS_HTML -> isHtml.
Not sure the best way here.