Question: Detail the relationship with `Project`/`Select` and SchemaBound `By`

[veeg]

Currently, the Project and Select traversals do not have a SchemaBound equivalent.

Gremlin.Net.CosmosDb/src/Gremlin.Net.CosmosDb/ITraversal.Extensions.cs

Lines 373 to 376 in 94e1fe8

	public static GraphTraversal<object, IDictionary<string, E2>> Project<E2>(this ITraversal traversal, string projectKey, params string[] otherProjectKeys)
	{
	return traversal.AsGraphTraversal<object, E2>().Project<E2>(projectKey, otherProjectKeys);
	}

While the By steps, which really go hand-in-hand with the Project/Select, have SchemaBound equivalents:

Gremlin.Net.CosmosDb/src/Gremlin.Net.CosmosDb/ISchemaBoundTraversal.Standard.Extensions.cs

Lines 135 to 146 in 94e1fe8

	public static ISchemaBoundTraversal<S, E> By<S, E>(this ISchemaBoundTraversal<S, E> traversal, IComparator comparator)
	{
	return traversal.AsGraphTraversal().By(comparator).AsSchemaBound();
	}
	/// <summary>
	/// Adds the by step to this <see cref="GraphTraversal{SType, EType}"/>.
	/// </summary>
	public static ISchemaBoundTraversal<S, E> By<S, E>(this ISchemaBoundTraversal<S, E> traversal, IFunction function, IComparator comparator)
	{
	return traversal.AsGraphTraversal().By(function, comparator).AsSchemaBound();
	}

Can anyone describe why we cannot have a SchemaBound Project traversal? Or is it simply an oversight/NYI?