Support resource-typed UUID parameters

Because a UUID parameter is just a string it's not possible to do things like {get_attr: [<uuid>, <attr>]} for resource external to the template being run. If a new parameter type were supported that required both a UUID value and an resource type value, the above type of construct might be possible (though I can imagine reasons that would make it difficult).