Include template arguments in instantiations' names (support marking "nested" instantiations as opaque)

Follow up to #773

To fully support template instantiations, and particularly template instantiations where a template argument is another template instantiation, with our various flags that depend on names (eg marking things opaque) we need to stop making template instantiations just use their template definition's name and start appending their template arguments.

The catch is that there are a bunch of places that assume that the names we return are valid rust identifiers and don't have characters like < in them. I kind of feel like we want multiple name-getting traits and/or multiple different name-getting methods on the ItemCanonicalName trait. Or maybe even extending the ItemCanonicalPath to return a tree rather than a vec so we can properly represent paths with instantiations and have each instantiation argument also be a path...

Anyways, after #773, we can make certain instantiations opaque, like Rooted<SavedFrameCache>, but not any "nested" instantiations, like Rooted<Cache<SavedFrame>>. Supporting the latter requires figuring out this naming mess.

Start with issue #773, then inspect the ItemCanonicalName trait and ItemCanonicalPath references mentioned here. Determine how nested template instantiations should represent their arguments without breaking callers that require Rust identifiers. Done means nested names such as Rooted<Cache> are represented and can be marked opaque.