Less mess up potential when registering middleware and controllers by making the order of registration irrelevant

**Is your feature request related to a problem? Please describe.**
When the controllers are registered before the middlewares the middlewares don't work or kick into action. I was confused about this and this is a potential for frustration and wasted time debugging.

**Describe the solution you'd like**
The order of registration becomes irrelevant.

**Describe alternatives you've considered**
Providing informative information via the logger on at least warning level.

**Additional context**

Working code sample:

```
public void setupServer(HTTPServer httpServer) {
httpServer.middleware("auth", new AuthenticationMiddleware());
httpServer.beforeAny("/api", new AuthenticationMiddleware());
httpServer.controller(HttpController.class, RootController.class.getPackage());
}
```

Unexpetedly broken sample:

```
public void setupServer(HTTPServer httpServer) {
httpServer.controller(HttpController.class, RootController.class.getPackage());
httpServer.middleware("auth", new AuthenticationMiddleware());
httpServer.beforeAny("/api", new AuthenticationMiddleware());
}
```

Commencez par les points d’entrée d’enregistrement de HTTPServer présentés dans setupServer : controller, middleware et beforeAny. Suivez l’impact de l’ordre d’enregistrement sur l’activation du middleware, puis définissez l’achèvement de sorte que les deux exemples de code appliquent le middleware de manière équivalente ; envisagez le journal d’avertissement demandé comme solution alternative si l’indépendance vis-à-vis de l’ordre n’est pas réalisable.

Rédigé par le modèle d'indexation à partir du texte de l'issue.