Refactor CloudStackTemplate object in template.go

**What would you like to be added**:
I would like to refactor the resource CloudStackTemplate because it currently contains within itself a ResourceFetcher, which is confusing. Why would a template contain a resource fetcher? It doesn't make sense. Some nomenclature is inconsistent, or perhaps the Template doesn't really need the ResourceFetcher

**Why is this needed**:
The current nomenclature/design doesn't make sense and leads to confusion and bad coding practices.

Start in template.go by reading CloudStackTemplate and its embedded ResourceFetcher, then trace the related nomenclature and callers. Clarify whether the ResourceFetcher belongs in the template design and define consistent naming before changing the object; done means the ownership and terminology are coherent without breaking its uses.

Written by the indexing model from the issue text.