FEAT: Minimal APIs implementation

[CesarD]

Description

The classic Controllers implementation is replaced by the new, more modern and performant Minimal APIs implementation.

Related Issue

Closes #56.

Motivation and Context

As explained in #56, the Minimal APIs implementation brings improved performance to the request execution because of the reduced amount of dependencies they provide. They are also more flexible to make this a better fit even for smaller projects as they are easy to compose and have a better system to document them in Swagger.

How Has This Been Tested?

This should be transparent and the endpoints respond exactly as the ones provided by the Controllers.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.