[task based] Rework groups by wildcards

[Bogdan Dobrelya]

We shall use this [0] example wildcard pattern every place we're enumerating all of the possible groups. And for plugins, one might exclude any custom roles being brought in by a plugin, if he/she doesn't want them to be wildcarded as well.

This would eliminate great confusion for Fuel / plugins developers, when trying to understand long role lists put in many places.

[0] https://review.openstack.org/#/c/272618/3/deployment/puppet/osnailyfacter/modular/fuel_pkgs/tasks.yaml

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/273596

[Bogdan Dobrelya (bogdando)]

Will not be fixed as custom roles from plugins should not be different from other existing roles, hence wildcards can not be used, see http://lists.openstack.org/pipermail/openstack-dev/2016-February/086903.html

[OpenStack Infra (hudson-openstack)]

Change abandoned by Kyrylo Galanov (<email address hidden>) on branch: master
Review: https://review.openstack.org/273596

[Kyrylo Galanov (kgalanov)]

All Fuel-native tasks should be placed under 'core' group. After that these tasks can be specifid in tasks.yaml like:
    groups: ['/core:.*/']