feat: Traffic Influence support

Paris Stentoumisrequested to merge
refactor/traffic-influence-work into develop

Summary

Adds Traffic Influence network-capability support on the activate path, including resolving target.application_server from a deployed workload before TF-SDK activation, and aligns QoD / Traffic Influence instance monitors to emit CAMARA-style capability_status (and related info) in event metadata / result backend.

Changes

  • Platform catalog: bootstrap traffic-influence capability (CapabilityKind.TRAFFIC_INFLUENCE).
  • Activation:
    • TrafficInfluenceActivationSpec — requires device IPv4 + application_reference; validates traffic-influence fields.
    • ApplicationServerResolver — if application_server IP is missing, resolve it from an active workload instance (pinned app_instance_id, or oldest active instance in zone) and take the first endpoint IPv4.
    • Wire resolver into NetworkCapabilityActivate / databus dependencies; persist resolved parameters on the capability instance snapshot.
  • Catalog port: ServiceSpecificationRepository.get_by_ref (+ SQLAlchemy adapter) for app lookup by ref.
  • Instance monitor: for QoD and Traffic Influence, publish capability_status (AVAILABLE / UNAVAILABLE) and capability_status_info when useful (duration_expired, network_terminated); mirror status into result_summary.backend.
  • Tests: unit coverage for resolver, activate, activation specs, and monitor; databus integration coverage for traffic-influence activate with app-server resolution.

Merge request reports