Extend UI to support a curie-curie view to help with Translator provenance

While adding provenance to the RDF would be very useful (#174), I think Translator's use-case can be met using the frontend: our problem is that we have curie-predicate-curie edges in the graph that connect subClassOf/part_of relationships that we don't have provenance for -- for example, we might have the edge [MONDO:0014036 "Alzheimer disease 17"](http://purl.obolibrary.org/obo/MONDO_0014036) rdfs:subClassOf [MONDO:0004975 "Alzheimer disease"](http://purl.obolibrary.org/obo/MONDO_0004975) from Ubergraph, but we don't currently have any way to indicate the provenance for this, apart from linking to https://github.com/INCATools/ubergraph or https://incatools.github.io/ubergraph/

What would be great for us is if we had some way to call https://incatools.github.io/ubergraph/edge?subject=MONDO:0014036&object=MONDO:0004975 and get a display that includes both those CURIEs and the relations between them -- we could send the predicate as well, but ours would be the Biolink predicate, which might not map exactly to RDF. If we had that, we could have our UI automatically generate these URLs when the user looks for this provenance, and then they could jump to Ubergraph to understand which ontologies asserted this, whether its direct or indirect, and any other relevant information.

I'm going to share this with our UI team to see if they like this idea and will let you know what they say -- please don't start working on it until we're sure this would meet our needs!

Wait for the UI team's confirmation before starting. Review the existing frontend flow around the Ubergraph edge URL, using /edge?subject=...&object=... as the proposed entry point; done means a view can display both CURIEs, their relation, and the provenance information returned for that edge.

Written by the indexing model from the issue text.