watch a collection of configs instead of a single one

[dennisjbell]

By specifying a pattern for config types and names, collecting them in a set order (ie alphabetical or numeric id), then comparing the sha sum of the conglomerate, the pipeline can pick up addition or removal of configurations, not just changes to specific configs. This is important for handling multiple named runtime configs where each config is defined for its purpose, for example.

Pattern could be something like 'cloud,runtime@*', which would detect only the default cloud config, and all runtime configs, but no cpi configs.