refactor: improve global architecture

[Turn0xx]

• run npm run test and npm run benchmark
• tests and/or benchmarks are included
• documentation is changed or added
• commit message and code follows the Developer's Certification of Origin
  and the Code of conduct

#52

[Turn0xx]

This PR introduces a modular architecture, organized by functional domains.
Each modules encapsulate its own declarations / definitions.

This is the actual structure that i'm going to follow:

modules
├── accounts
│   ├── index.route.ts
├── auth
│   ├── auth.service.ts
│   ├── controllers
│   │   ├── index.ts
│   │   └── login.controller.ts
│   ├── index.route.ts
└── tasks
       ├── index.route.ts

Each module is going to have

• A bunch of controllers (generally one controller per route), who consumes services through the fastify instance.
• One or more services, implemented as plugins.
• Route file that serve as the api entry points

Wdyt on this approach ?

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[jean-michelet]

I think having a controllers directory is a bit too much for now.
We can start by creating services to reduce controllers logic and we'll see if we need a controllers dir later.
But you can create a services dir.

[Turn0xx]

@jean-michelet You mean to much for the auth module or for all modules ? yeah for auth module just an index file would do the work. However i think for other modules like tasks, we can create multiple controller files per action area.

[jean-michelet]

Are you sure it will not break ts inference? One file by controller function is too much I think.

[Turn0xx]

Are you sure it will not break ts inference?

What do you mean by ts inference ?

One file by controller function is too much I think.

It's not really one file by controller function but one file by action area.
But for this demo you are right there is not really a lot of actions area per module so i'm going to make just 1 file.

And the same thing for services i think.

[mcollina]

This is an antipattern. You are splitting the route code from its definitions, and you shouldn't really do that at all, as they are tightly coupled together.