Keep FM internal deployment status checks compatible with adapter signatures so federated kubernetes smoke tests stop failing with 500s.

 
Replace the Connexion + MongoDB service-resource-manager-implementation
tree with src/srm: FastAPI, SQLAlchemy/Postgres, NATS, and a clear hexagonal architecture.
 
Persistence
- Migrate durable state from MongoDB to PostgreSQL
- Async SQLAlchemy repos for catalog, topology, and runtime inventory
 
Messaging
- Introduce NATS as the platform databus (publisher, durable subscriber,
  connection manager)
- Command/event envelopes with schema_version and federation-context
  validation
- Async handlers for deploy/terminate and network-capability activate/
  deactivate, with answers published back on the bus
 
Sync vs async operations
- Synchronous northbound REST (/internal and health) for queries and
  service-specification CRUD (immediate HTTP response, RFC 7807 errors)
- Asynchronous southbound lifecycle via NATS commands; long-running
  work (deploy, terminate, capability activate/deactivate) is accepted
  on the bus and completed with follow-up events (including FM operation
  completed where federation applies)
- OpenOp TF-SDK wired as the control-path adapter factory for sync
  control-plane calls inside those async flows (service and network
  capability lifecycle, location retrieval, traffic influence)
 
Other develop capabilities
- Service specification catalog APIs and catalog update events
- Traffic Influence and Location Retrieval
- Control-path bootstrap aligned with TF-SDK 2.0.0
- CI qualification for TF-SDK consumer builds

SRM Release 2.0.0

See merge request !48