Support Wildcard host matching for hst:platform

NOTE: This might (should?) NOT be needed any more!

I have given it some more thoughts, and instead of a * matcher for the host in the cms, we might have need something else since we have an interesting challenge wrt host groups.

Instead of doing the wildcard matching, we can make explicit hosts and host groups below hst:platform. Then the host group for the matching cms host will also be the host group for which other hst configuration will be scanned for their channels (mounts). This means we can get rid of the hst:cmslocations completely....finally!

Next to that, this means that for a certain cms host, say, cms.exmaple.com, we have 1 single host group for all hst configurations, and for another one, say, cms.acct.example.com, we have another host group.