Configuring the Template Attribute Resolver to consult its dependencies.

[Cantor, Scott]

> We initially thought that the work had been done and that the
> SourceAttributes were not needed (as well as being spurious), but that's not be
> the case.  Furthermore it cannot be made that way in V3.  The issue is that as
> far as the code (at the api level) is concerned the Dependencies are returned as
> a Set, whereas for obvious reasons the template requires a List.

Why would it need to be a List? I don't think that's true, there's just a goofy V2 feature using that assumption to build a template if one isn't provided, which I don't think is really a necessary feature.

-- Scott