[ENHANCEMENT]: Refactor the whole frontend structure to be simplier

[leofvo]

Description

Contributing on frontend is actually a disaster.
We are duplicating a lot of things and adding more and more useless code that will be unmaintenable in few months.
As we are rethinking our application and try to focus on major things to get done, refactor the folder structure could improve our developement flow and efficiency.

Of course there is a price to do that, and it's actually to big to be one-shot.
With @MaloPolese we are proposing to get a more simplier approach and use the same folder structure as nextjs.

We aim to reach a folder structure like this one in src folder:

• main.tsx
• config shared constants for the whole app
  • constants
  • routes the routers and routes definitions
• environments infrastructure environments stuff
• i18n
• styles scss properties
• app polyflix application
  • pages
  • layouts
  • contexts
  • hooks
  • styles
• studio studio stuff
  • pages
  • layouts
  • contexts
  • hooks
  • styles
• shared shared stuff between 2
  • components
  • hooks
  • services
  • contexts
  • types

Of course a folder structure isn't sufficient to get things orderned, we should adopt a new way to create and place component.
In each folder you will find domains specific folder
for example in shared/components:

• common shared components between all domains
• videos components specific to video
• courses
• users

To adopt this new architecture we will need to move things progressively.

[MaloPolese]

I think that app/components is only the components for polyflix.
If you want some shared components between polyflix and studio maybe have a lib or a folder like core or shell
In this folder you can add all the components / env / hooks / api services .... shared between all app

[MaloPolese]

And the idee is cool. but, right now i don't think that it have a height priority. Maybe we need to do the costing of the task first