Incorrect default_user_domain and default_project_domain variables used

[Laurie Fisher]

Within the masakari and tacker ansible roles the default_project_domain_id and default_user_domain_id are used as values for os_project_domain_name/project_domain_name and os_user_domain_name/user_domain_name respectively.

This is fine if you use the Default domain as that domain has a special ID of "default" and the values are case insensitive but if you use a domain other than default then the ID will be a UID and fail to authenticate.

https://opendev.org/openstack/kolla-ansible/src/ansible/roles/masakari/templates/masakari.conf.j2#L10-L11
https://opendev.org/openstack/kolla-ansible/src/branch/master/ansible/roles/tacker/templates/tacker.conf.j2#L39-L40

While resolving this bug I'd suggest standardising the use of user_domain_name and project_domain_name instead of user_domain_id and project_domain_id. Doing so will make it easier to use a domain other than Default for OpenStack services seeing as the kolla variable default_project_domain_id is a static global variable and it's not possible to determine the new domain UID before the deploy.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/kolla-ansible/+/892385