fix: add fake URI path to navigation properties requests

This is required if the related EntityVerticle is serving multiple
entities and needs to decide which type should be returned. This is a
workaround until inter-verticle entity exchange [1] has been improved.

[1] https://github.com/SAP/neonbee/blob/main/docs/milestones/E1_MS02_entity_exchange.md

src/main/java/io/neonbee/internal/processor/odata/NavigationPropertyHelper.java

@@ -13,6 +13,7 @@
 import org.apache.olingo.commons.api.edm.EdmEntitySet;
 import org.apache.olingo.commons.api.edm.EdmNavigationProperty;
 import org.apache.olingo.commons.api.edm.EdmReferentialConstraint;
+import org.apache.olingo.commons.api.edm.FullQualifiedName;
 import org.apache.olingo.server.api.ODataApplicationException;
 import org.apache.olingo.server.api.uri.UriResource;
 import org.apache.olingo.server.api.uri.UriResourceNavigation;
@@ -39,7 +40,8 @@ public final class NavigationPropertyHelper {
      */
     public static Future<List<Entity>> fetchReferencedEntities(EdmNavigationProperty navigationProperty, Vertx vertx,
             RoutingContext routingContext) {
-        DataRequest req = new DataRequest(navigationProperty.getType().getFullQualifiedName(), new DataQuery());
+        FullQualifiedName fqn = navigationProperty.getType().getFullQualifiedName();
+        DataRequest req = new DataRequest(fqn, new DataQuery(fqn.getNamespace() + "/" + fqn.getName()));
         return requestEntity(vertx, req, new DataContextImpl(routingContext)).map(EntityWrapper::getEntities);
     }