chore: remove prettier and eslint in favour of biome

[maschad]

Closes #2195

Pros

• Biome would centralize all our linting and formatting into one file i.e. the biome.json
• Biome is ~15x faster than ESLint and ~20x than prettier
• Addresses a lot of the inconsistencies with prettier

Cons

• Extremely disruptive change with no value add
• Not nearly as widely adopted
• It's not stable yet nor is there support for plugins.

[petertonysmith94]

Maybe I'm missing something but is this not removing all the rules we currently have in place? I can't see a biome.json file which has all the rules migrated from eslint 👀

Also for the apps and templates, I believe these should be self sufficient. So maybe, we should add biome as a devDependency and add the relevant configuration files.

[arboleya]

I second what @petertonysmith94 said. If we are swapping libraries, it must be a drop-in replacement.

Also, do we really want to push biome on others via the create-fuels template? I haven't thought much about it, but my instinct says we should not.

[maschad]

Agreed @arboleya and @petertonysmith94 the intention is to migrate the rules over, this initial step was just removing eslint. Once that migration is complete I think the PR will be ready for review. I appreciate the initial feedback on PR especially since it touches so many files.

[maschad]

Thanks for the first pass @nedsalk , a lot of these were actually bugs hence the compilation issues. I've addressed them, I'll open the PR for review when ready.

[maschad]

I think this project would be good to revisit in the future but I don't think it's worth the change yet based on reasons listen in the description.