Vite migration: ESLint fixes

[NextFire]

Follow-up to #154

eslint errors/warnings and applied fixes:

React no-unused-vars

Remove unused React imports.

no-class-assign and other no-unused-vars

Disable these two rules. The second error was often raised on unused function arguments or object destructured properties that I believe were left for better readability and self-documentation.

no-case-declarations

Add {}.

no-undef

Add // eslint-disable-next-line.
This error was raised on DAKARA_VERSION, DAKARA_BUGTRACKER and DAKARA_PROJECT_HOMEPAGE that are defined in vite.config.js.

react/display-name

Add // eslint-disable-next-line on four decorators in https://github.com/NextFire/dakara-client-web/blob/vite-eslint/src/components/adapted/ReactRouterDom.jsx.

react/no-unescaped-entities

Escape characters.

react-refresh/only-export-components

Name some default exports + move two shared const to https://github.com/NextFire/dakara-client-web/blob/vite-eslint/src/utils/permissions.js.

react/prop-types

Add or complete propTypes on various components.
I often had to guess when to add isRequired or not…

[Neraste]

I've to check if everything works as expected.

Add // eslint-disable-next-line.
This error was raised on DAKARA_VERSION, DAKARA_BUGTRACKER and DAKARA_PROJECT_HOMEPAGE that are defined in vite.config.js.

These variables are exctracted from package.json, if there is a better way to pass them, I'm open to it.

[Neraste]

This is cleaner.

[Neraste]

I just merged #156, so you can re-apply the linting. Maybe you should create a new PR instead?