Add configurable HTTP server adapter

[ricardo-devis-agullo]

Summary

• add server.adapter/server.options config with Express defaulting
• route registry adapter creation through a server adapter normaliser
• add unit coverage and update HTTP server adapter status for phase 5

Verification

• npm run build
• npm run test -w oc

[ricardo-devis-agullo]

@copilot review

[Copilot]

@copilot review

Here's a summary of the review findings:

Fixed (7c77241 → follow-up commit):

• options-sanitiser.ts: the two follow-up if (options.server && ...) guards were redundant — options.server is always truthy after the first block sets it. Removed the redundant options.server && conditions.

Observations (no change needed):

• server-adapter.ts: isHttpServerAdapter only checks native, listen, and httpServer out of the ~15 interface methods. This is intentionally minimal (mirrors duck-typing patterns), but an incomplete adapter would fail later with less clear errors. Could tighten the check in a future pass if desired.
• express-adapter.ts: the options?: unknown parameter + runtime narrowing handles backward compat (legacy number/string port vs new { port } object) correctly.
• types.ts: server.options?: unknown loses generic type info compared to the storage adapter's T-based approach, but is acceptable since server adapters are more varied and the type is captured at the factory level.
• http-server-adapter-status.md at the repo root: if this is intended as a public migration guide, it belongs; if it's a private dev note, it can be removed.

No other issues found. Tests and build verified prior to submission (937 passing).