refactor: share lint rule options

[ematipico]

Summary

Fix #6018

This PR refactors the rule options, which are now generated and shared among rules.

• the codegen will crate an option file only if the rule doesn't exist
• updated the codegen for the generation of the rule
• the rule options can't depend on *_syntax crates anymore

Test Plan

No changes to the users, the CI should stay green.
I will update the contribution guide after we merge this one, which is already big enough

[Conaclos]

I committed some changes to improve useNamingConvention options.

Note: I had to remove your last merge commit because it was removing features committed on main leading to many errors.

[Conaclos]

I performed the merge with main.

[codspeed-hq]

CodSpeed Performance Report

Merging #5543 will not alter performance

_{Comparing refactor/shared-rule-options (a79022d) with main (4b501d3)}

Summary

✅ 114 untouched benchmarks

[ematipico]

What do you think of my solution?

[Conaclos]

What do you think of my solution?

I am unsure how this could work once we promote the GraphQL nursery/useNamingConvention to style.
Should the GraphQL rule use the same option as the JS rule? What if we forget to do so? Would that result in a runtime error?

Also, some options make sense only in a given language. Should we then ignore them in the rules of a different language?

[ematipico]

What do you think of my solution?

I am unsure how this could work once we promote the GraphQL nursery/useNamingConvention to style. Should the GraphQL rule use the same option as the JS rule? What if we forget to do so? Would that result in a runtime error?

Yes, they will inherit the same options, it's up to the rule to use them. There shouldn't be a runtime error.

Also, some options make sense only in a given language. Should we then ignore them in the rules of a different language?

That's a valid concern that we haven't tackled yet. Imho, if an option makes sense only for a given language, then the rule should have a very specific name that implies that it's used only in JavaScript files. The options could also be divided into different languages, e.g.

{
  "useNamingConvention": {
		"javascript": {} // current options
		"graphql": {} // options for graphql
	}
}

[ematipico]

Regardless, as for now, I think we should rename the lint rule inside graphql.

[changeset-bot]

⚠️ No Changeset found

Latest commit: a79022d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[arendjr]

🚀