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());
}
```

从 setupServer 中显示的 HTTPServer 注册入口开始：controller、middleware 和 beforeAny。跟踪注册顺序如何影响 middleware 的激活，然后将完成标准定义为两个代码示例都以等效方式应用 middleware；如果无法实现与顺序无关，则将请求的警告日志作为替代方案考虑。

由索引模型根据 Issue 内容生成。