Fix documentation for remote projection

- no more property schemas
- concurrency config

Author: Mats-SX

doc/modules/ROOT/pages/gds-session.adoc

@@ -126,10 +126,9 @@ The Cypher query must contain the `gds.graph.project.remote()` function to proje
 gds.graph.project(
     graph_name: str,
     query: str,
-    nodePropertySchema: dict[str, GdsPropertyTypes],
-    relationshipPropertySchema: dict[str, GdsPropertyTypes],
-    undirectedRelationshipTypes: list[str],
-    inverseIndexedRelationshipTypes: list[str],
+    concurrency: int = 4,
+    undirected_relationship_types: Optional[List[str]] = None,
+    inverse_indexed_relationship_types: Optional[List[str]] = None,
 ): (Graph, Series[Any])
 ----
 
@@ -139,8 +138,7 @@ gds.graph.project(
 | Name                            | Optional | Description
 | graph_name                      | no       | Name of the graph.
 | query                           | no       | Projection query.
-| nodePropertySchema              | yes      | Mapping of node property names to their types.
-| relationshipPropertySchema      | yes      | Mapping of relationship property names to their types.
+| concurrency                     | yes      | Concurrency to use for building the graph within the session.
 | undirectedRelationshipTypes     | yes      | List of relationship type names that should be treated as undirected.
 | inverseIndexedRelationshipTypes | yes      | List of relationship type names that should be indexed in reverse.
 |===
@@ -165,15 +163,6 @@ Instead, the graph name is provided to the `gds.graph.project()` endpoint.
 For full details and examples on how to write Cypher projection queries, see the https://neo4j.com/docs/graph-data-science/current/management-ops/graph-creation/graph-project-cypher-projection/[Cypher projection documentation in the GDS Manual].
 
 
-==== Property schemas
-
-The optional parameters `nodePropertySchema` and `relationshipPropertySchema` are useful when projecting graphs with multiple node labels or relationship types which have distinct property sets (_heterogeneous graphs_).
-
-If these parameters are not provided, the type of each property is inferred from the first row of data seen by the projection function.
-For homogeneous graphs this is usually sufficient, while for heterogeneous graphs it is not.
-For this reason, we recommend to always use the property schema parameters.
-
-
 ==== Relationship type undirectedness and inverse indexing
 
 The optional parameters `undirectedRelationshipTypes` and `inverseIndexedRelationshipTypes` are used to configure undirectedness and inverse indexing of relationships.
@@ -226,8 +215,8 @@ With the `gds` GDS Session active, project the graph and specify node and relati
 from graphdatascience.session import GdsPropertyTypes
 
 G, result = gds.graph.project(
-    "my-graph",
-    """
+    graph_name="my-graph",
+    query="""
     CALL {
         MATCH (u1:User)
         OPTIONAL MATCH (u1)-[r:KNOWS]->(u2:User)
@@ -246,8 +235,6 @@ G, result = gds.graph.project(
       relationshipProperties: properties(rel)
     })
     """,
-    nodePropertySchema={"cost": GdsPropertyTypes.DOUBLE},
-    relationshipPropertySchema={"since": GdsPropertyTypes.LONG, "price": GdsPropertyTypes.DOUBLE},
 )
 ----
 
@@ -263,12 +250,13 @@ For instance, you can run the PageRank and FastRP algorithms on the projected gr
 gds.pageRank.mutate(G, mutateProperty="pr")
 gds.fastRP.mutate(G, featureProperties=["pr"], embeddingDimension=2, nodeSelfInfluence=0.1, mutateProperty="embedding")
 
-# Stream the results back together with the `name` property fetched from the database
+# Stream the results back together with the `name` property fetched from the database
 gds.graph.nodeProperties.stream(G, db_node_properties=["name"], node_properties=["pr", "embedding"])
 ----
 
 For a full list of the available algorithms, see the https://neo4j.com/docs/graph-data-science-client/{page-version}/api/[API reference].
 
+
 == Remote write-back
 
 The GDS Session's in-memory graph was projected from data in AuraDB, so write-back operations will persist the data back to the same AuraDB instance.