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 の本文から書いたものです。