[ESLint plugin] Add a rule to enforce folder architecture on frontend

[ijreilly]

Scope & Context

Follow: https://docs.twenty.com/contributor/frontend/folder-architecture and enforce it with linter We have diverge a bit from the docs, let's what we have in the project right now. If there are some inconsistencies let's discuss them here.

Bonus :

• not sure if there is a way to nicely highlight these "standard" folders in VSCode with colors to show that they are different

Technical inputs

See if there is an existing ESLint rule to enforce it If not create a custom rule in tools/eslint-rules

[gitstart-connector[bot]]

Issue synced into GitStart. Please review, edit and hand it off to GitStart by following this link.

[ijreilly]

Input from @charlesBochet

We should

1. create the rule as a warning
2. check folder by folder to avoid big conflicts on the project
3. change the rule as error

[ijreilly]

@gitstart-twenty For this issue please open PRs folder by folder if relevant and not a big PR with a lot at once, otherwise we will have too much conflicts

[ijreilly]

(Recreating this issue to help sync with @gitstart-twenty ticket studio)