Use new code formatting approach since ESLint deprecated all formatting rules

[chrismayer]

Since V8.53, ESLint team decided to deprecate all formatting rules. More info can be found on this official announcement.
To keep it simple, those rules will stay at least in version 9 of ESLint but will not receive any updates anymore. Those rules should be abandoned in favor of a code formatter OR replaced by the rules defined in [@stylistic/eslint-plugin-js](https://eslint.style/packages/js). This package contains all the deprecated rules and will be maintained. However, as our main dependencies (eslint-plugin-vue and eslint-config-standard) don't make use of those rules yet, it is better to wait before making the transition on our side...

This issue is derived from #377 and the text above was initially provided by @sronveaux .

[sronveaux]

Just a follow-up on this one, it seems like StandardJS is kind of abandoned and that a lot of people transit to neostandard which tries to align with current StandardJS with minor changes (mainly due to plugins not yet transited to the new configuration format) which are made by the community through an open governance.
It is still in an early stage but I think we should keep an eye on it if we decide to keep aligned to StandardJS as it already makes use of the rules defined in @stylistic/eslint-plugin-js.

We should however wait for V1 to be out I think and also perhaps for Wegue to be transited to Vite if possible so eslint-plugin-vue could be removed easily.

Don't hesitate to give your opinion about this one!