Simplify APIs endpoints

[hishamco]

This PR intends to simply use API endpoints. Currently, each end point has its file, which is suitable for small but not for enterprise because it's a miss. That's why Controller & ApiController organize the actions into a single unit. Sometimes, we might need to use partial classes if there are many endpoints for a particular entity.

Another good thing about the current implementation is that it groups the APIs and reduces the amount of the configuration, such as API prefix, group name, and setting authentication scheme.

FYI, we could use the source generator to register the end point. If we do so

@sebastienRO,s your feedback please

[MikeAlhayek]

@hishamco personally I rather keep one file per request for endpoint. I think it is a much cleaner approach.

[sebastienros]

It's not "simplifying", it's adding magic that people would have to learn/discover to understand how that works. I had to. So if you have a class named ContentEndpoints then the url will magically become api/content because your class ends with Endpoints.

[sebastienros]

We need to have a discussion about how endpoints are grouped and the classes named though. @MikeAlhayek likes them in different files, I like them grouped by entity.

[hishamco]

I might agree with you to group them by entity, and we could use a partial class in case the code is too long

[hishamco]

I had to. So if you have a class named ContentEndpoints then the url will magically become api/content

The prefix could be configurable as well as the group name, but I follow the conventions over the configuration pattern