Chasers to provide more robust methods to get translated paths

There is currently a useful method for returning a mapping of translated Maya DagPaths to USD paths, using GetDagToUsdMap. It could be more useful to be able to call methods like GetDagPath() by providing the USD path and GetUsdPath() by providing the DagPath. It's also important to be able to fetch DG nodes, like GetDepNode() by providing the USD Path and GetUsdPath() by providing just the DG name.

This is especially important when maya nodes have namespaces, since they will either be stripped in USD or sanitized by replacing ':' with '_', which makes it difficult to figure out which maya node belongs to which usd node and vise versa.

The translator could keep a running map of all translated nodes and where they went in USD and either make that private and expose functions like I suggested or just make the mapping public, but not limited to DagPaths.

Start by locating GetDagToUsdMap and tracing how the translator records Maya DAG, dependency-graph, and USD paths. Compare the requested GetDagPath(), GetUsdPath(), and GetDepNode() lookups, including namespaced and sanitized node names. Done means the chosen mapping API supports the requested path and node inputs in both directions.

Written by the indexing model from the issue text.