feat: create "biome" hook, preserve "rome" hook as alias

[oxcabe]

This PR does the following:

• Renames the "rome" hook to "biome", correcting any references to the rome tool.
• Sets the "rome" hook as an alias to the "biome" hook as a backwards compatibility guard.
• Adds relevant documentation to the README.

Fixes #428.

[sandydoo]

@oxcabe, could you please remove all the code formatting changes? The diff should be readable and contain just the changes you're proposing. Thanks!

[oxcabe]

Sure thing, I'm not even sure when the files got formatted 😅

[sandydoo]

I think the better approach here would be to use mkRenamedOptionModule to rename rome -> biome. You get the alias and people will be prompted to switch.

If you feel like an alias (with no warning) is more appropriate for now, then you can use mkAliasOptionModule instead.

There's no need to have both rome and biome in config.hooks.

[oxcabe]

I know it's failing as of my last commit. Currently trying to figure out by myself what am I doing wrong and why 👍🏼

[oxcabe]

I think the better approach here would be to use mkRenamedOptionModule to rename rome -> biome. You get the alias and people will be prompted to switch.

Implemented this approach. For some reason, the deprecation warning is not appearing when enabling the hook:

rome.enable = true;

There's no need to have both rome and biome in config.hooks.

I can't seem to make it work without having config.hooks entries for both tools. By omitting rome there, the following error appears:

error: The option `hooks.rome.entry' is used but not defined.

[oxcabe]

From the failing build:

pre-commit-run> - hook id: nixpkgs-fmt
pre-commit-run> - files were modified by this hook

@oxcabe, could you please remove all the code formatting changes? The diff should be readable and contain just the changes you're proposing. Thanks!

What should I do here?

[sandydoo]

See if you can move that rec around to stop it from reformatting everything. If not, then commit the formatting changes.

[oxcabe]

Ready!