fix: endpoint name issues for dkr.api and others

[DannyBlazejczak]

Issue #, if available:

Description of changes:

This is fixing 2 issues with the endpoints:

Issue 1:

• endpoint for ecr.dkr was incorrectly named ecr-dkr, it results in this error:
  "The Vpc Endpoint Service 'com.amazonaws.ap-southeast-2.ecr-dkr' does not exist (Service: Ec2, Status Code: 400 ..."
  Solution 1:
• It is incorrect to assume that all endpoint service names use a dash, e.g. these services all have dots, not dashes:
  ecr.drk, ecr.api, airflow.api, airflow.env, airflow.ops, sagemaker.api, sagemaker.runtime-fips
  There are no fast rules here, take the input from the configuration instead.

Issue 2:

• For the privateDnsName using 'ecr.dkr' resolved wrongly to '*.dkr.ecr.ap-southeast-2.amazonaws.com.', and results in this error:
  "Invalid request provided: Creation of hosted zone with a wildcard domain name is not supported. (Service: Route53, Status Code: 400"
  Soltion 2: (did not work)
• The tool discoverEndpoints was ran but did not update the privateDnsName for the endpoint.
  Solution 2b:
• To remove the *. prefix which is invalid for DNS names. There are many endpoints with this issue.
• Hence removing the *. in front of the dns name.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.