Changing peer dependencies (breaking)

This feature allows to avoid spinning up HTTP server when only HTTPS one
is needed.
It should enable best practices in the establishing secure communication
channel.

Changes to `ServerConfig` type:
- `server` prop renamed to `http`
- nested props `jsonParser`, `upload`, `compression`, `rawParser` and
`beforeRouting` moved to the top level
- all that included into the automated migration (ESLint rule) for v21

This should ease declaration and enable future improvements like #2099 

Making `createServer()` to return an object having `servers` property
instead of `httpServer` and `httpsServer`

No longer used, #2117

Due to #2137 deprecated

Due to #2144 

- [x] needs a migration script

- Default should be `get`;
- I'm also thinking to make it optional for `DependsOnMethod` case
- then the default would be the property of its constructor the endpoint
assigned to
- for that, `getMethods()` of Endpoint would return empty (which
technically it can) or `undefined`, and the decision making on method
would be delegated to Routing Walker.
- this, however, deviates from the initial concept and affect such
features as `testEndpoint` for CORS enabled endpoints, so that it could
not respond with its allowed methods without routing, OR decetralizing
the method decision making.
- the workaround might be moving CORS headers handling into
`initRouting`

Addressing to v21

Instead of `logger` and `getChildLogger`

Avoiding recursion should decrease memory consumption by replacing the
utilization of call stack to a stack of entities to process

https://www.nearform.com/insights/tracking-memory-allocation-node-js/

```
   ✓ Experiment for routing walker (2) 1247ms
     name             hz     min     max    mean     p75     p99    p995    p999     rme  samples
   · current    3,691.20  0.2053  2.7257  0.2709  0.2885  0.3817  0.4519  2.1826  ±1.49%     1846
   · featured  50,253.26  0.0123  5.8032  0.0199  0.0165  0.0423  0.1116  2.7895  ±7.10%    25127   fastest
```

Turned out that the performance is mostly affected by `assert(..., new
Error())` pattern, partially introduced by
#1371

Discovered during #2168

This reverts commit 9f1e0bf.

I wanna put all my recent performance findings into ESLint rules, so
that I could address them globally later

- Object.assign turned out to be significantly improved in Node 22, but
it's still faster for extending existing aggregator in a reducer. For
other cases spread is ok.

`http.Server | https.Server` —> `net.Server`, common ancestor

This reverts commit a65472f.

Due to #2128 , did not found those lines initially, but found during
work in #2175

New attempt for #1536 
Based on the discussion
#1193 (reply in thread)

It's publicly exposed, therefore I consider it breaking.
I wanna make the usage of that error easier.

Related to #2188 
Affects #2191 — should reduce shifting

needed for #2191 as a better way to handle responses array