Summary

This adds once of the nice to have listed in #2835

Proposed on discord: https://discord.com/channels/678763474494423051/978209399120216076/987343929231941673

The PR changes how the declare_rule is defined. Now the shape is different and it has a struct-like syntax:

declare_rule! {
    ///  Disallow labels that share a name with a variable
    pub(crate) NoLabelVar {
        version: "0.7.0",
        name: "noLabelVar"
    }
}

It also accepts another field, which is a possible deprecation reason. This will be useful in the future, when we want to ditch or change rules. It's not used anywhere yet, other than being part of the metadata:

declare_rule! {
    ///  Disallow labels that share a name with a variable
    pub(crate) NoLabelVar {
        version: "0.7.0",
        name: "noLabelVar",
		deprecated: "This rule wasn't safe, please use `noLalbelInVar`"
    }
}

The small downside of this approach is that the version is hardcoded, so the developer has to make sure to put the correct next version (usually the next minor). But, for now, I think it's a small price to pay compared on setting workflows and branches for multiple websites.

I also tweaked a bit the documentation cargo alias to include also rome_js_formatter, which will be deployed once the PR is merged.

I also moved the codegen of the configuration in another command called cargo codegen configuration. Having it in a separate command fixed an issue on CI, now some rules that were "missed" locally are now correctly added. I plan to add this command in the CI in another PR, to see if actually fixed the issue.

Test Plan

Check the rendered result