rapid-cdn: Handle correctly wildcard domains

While generating haproxy configuration (including it's CRT list) the specific
order of entries is used, so that wildcard domains end up last. Thanks to this
they work as a catch-all and allow specific domain to take precedence. Care
is taken to support *.example.example.com and *.example.com situation - so
tree like possibility of wildcards.

Anonymous in-place ACL are used per each domain, instead of per-shared
instance grouping in order to avoid situation like *.example.com and
example.com having single ACL, thus resulting with catch-all kicking in too
fast.

For the precision in the haproxy configuration and simplifcation of the regular
expressions the -m reg is used, so that host_only can be applied, which also
lowercases the hostname.

Notes:
 * test00cluster_request_instance_parameter_dict changed due to sorting slaves
   in test's requestSlaves
 * the test infrastructure has been improved to assure repetition of the
   situation
 * tests in TestSlaveHostHaproxyClash are asserting that correct domain AND
   that specific certificate have been used while serving given frontend
   configuration
8 jobs for master in 0 seconds
Status Job ID Name Coverage
  External
passed Cloudooo.UnitTest-Master

00:04:27

failed ERP5.StandaloneDeploymentScriptTest-Debian.Buster

00:39:07

passed SlapOS-Master.StandaloneDeploymentScriptTest-Debian.Buster

00:48:53

passed SlapOS.Eggs.UnitTest-Master.Python2

00:19:32

failed SlapOS.Eggs.UnitTest-Master.Python3

00:22:39

failed SlapOS.SoftwareReleases.IntegrationTest-Master

07:13:56

passed SlapOS.Theia.ResilienceTest-Master-ERP5

06:23:38

passed Wendelin.StandaloneDeploymentScriptTest-Debian.Buster

00:34:00