Nexus incoming services registry matching implementation

[pdoerner]

What changed?

Added matching implementations for Nexus incoming service CRUD APIs New matching logic is in incoming_service_manager which handles loading services and managing cached services. This component holds two service views in memory: a service list sorted by service ID and a map of service name -> service. The list is used to support pagination using the same ordering as persistence nexus_incoming_services table. The map is used for efficient lookups of a single service.

Why?

How did you test it?

Potential risks

None

Is hotfix candidate?

No