IRouter.GetVirtualPath alternative in EndpointRouting

Based on this topic:
https://github.com/dotnet/aspnetcore/issues/18883

The "IRouter.RouteAsync" alternative is "DynamicRouteValueTransformer.TransformAsync".

**What is the "VirtualPathData GetVirtualPath(VirtualPathContext context)" alternative for complex url generation?**

For example:
```
public override VirtualPathData GetVirtualPath(VirtualPathContext context)
{
var routeContext = context["context"] as new ProductListRouteContext();
var pathSegements = new List();
if (context?.Category?.PageName != null)
{
pathSegments.Add(context.Category.PageName);
}
// Add other pathSegements based on the context/filters...
return new new VirtualPathData(this, string.Join("/", pathSegments));
}
```
In my view:

`Url.RouteUrl("ProductList", new { context = Model.ProductListRouteContext });`

Start by reading the linked issue about EndpointRouting, then compare IRouter.RouteAsync and DynamicRouteValueTransformer.TransformAsync with the GetVirtualPath and Url.RouteUrl entry points shown here. Determine whether EndpointRouting exposes a supported alternative for complex URL generation; done means the alternative and its usage are clearly documented or the gap is explicitly defined.

Written by the indexing model from the issue text.