http client linking

[NTCoding]

Design a solution for HTTP linking - detecting connections from HTTP client calls (e.g. fetch()) to the endpoints they target. See issue #269 for the event handler linking solution. HTTP linking should be done at the same time.

Requirements

Cross-module HTTP links (internal)

Detect when a component calls another module's API endpoint via HTTP. Example from ecommerce-demo-app BFF domain:

• bff:useCase:PlaceOrderBFFUseCase → orders:api:handle (fetch to http://localhost:3000/orders)
• bff:useCase:PlaceOrderBFFUseCase → inventory:api:CheckStockEndpoint (fetch to http://localhost:3001/inventory/...)

External service links

Detect when a component calls an external service via HTTP. These are services outside the codebase with no corresponding extracted component. Example:

• bff:useCase:PlaceOrderBFFUseCase → Fraud Detection Service (http://fraud-detection-service.internal/api/check)
• bff:useCase:PlaceOrderBFFUseCase → Customer Service (http://customer-service.internal/api/customers/...)

Current gap

The BFF use case calls fetch() with hardcoded URL strings in private helper methods. No constructor injection, no typed dependencies. Current detection strategies (call graph, configurable patterns, async publish/subscribe) all require typed method calls or metadata — none can detect bare fetch() calls with string literal URLs.