feat(linter): implement noLowerCaseEnum

[eMerzh]

Summary

• it's globally accepted that enums should be in uppercase, although not a "spec requirement", some other tools have this lint.

please be indulgent, i'm a very noob in rust /o\

also there are no linked issue bc i'm not sure which one i should create.

Test Plan

see tests

[codspeed-hq]

CodSpeed Performance Report

Merging #4031 will not alter performance

_{Comparing eMerzh:gql_all_caps_enum (fc8a858) with main (2035efe)}

Summary

✅ 95 untouched benchmarks

[minht11]

I think could be handled by https://biomejs.dev/linter/rules/use-naming-convention/#typescript-enum-names ?

---

If you are planning on working issue yourself, you can open straight up and someone will assign you, but you do not need to wait for that. Though discussion can help to make sure you are going into right direction.

If you do not plan working on it but want it implemented:

1. For existing rules use ✅ Linter rules from other sources #3
2. If rule is completely unique open discussiong entry.

[eMerzh]

mmh i have no idea for the ts enums 🤔 even if those are Graphql enums? 🤔 and if you want differents rules between gql & ts?

[dyc3]

I'll defer to somebody else for what the name for this rule should be. There should also be a changelog entry for this.

[eMerzh]

thx for the quick review, I've added the changelog entry

[minht11]

I think originally the idea was that multiple languages can have the same rule. Like for example json language has useSortedKeys, the same rule could be implemented for javascript as well. noLowerCaseEnum could be part of useNamingConvention but for graphql, configuration would be separate for each language. As far as I know currently there are no rules like that, so there are a lot of unanswered questions.