test: update custom domain integration tests

[valerena]

The tests were outdated, so we updated domains and hosted zones, so we need to update the expected values here.

Issue #, if available

Integration tests were failing.

Description of changes

Updated the hosted zone and domain name for the tests, so the value of generated hashes for ApiGW Domain (depends on the domain name) and RecordSetGroup (depends on the hosted zone id) had to be updated.

Description of how you validated changes

$ pytest --no-cov --reruns 0 integration/combination/test_custom_rest_api_domains.py --prefix SamTranslatorLambda --internal --parameter-values template_parameter_values_new.yaml --stage prod
$ pytest --no-cov --reruns 0 integration/combination/test_custom_http_api_domains_test.py --prefix SamTranslatorLambda --internal --parameter-values template_parameter_values_new.yaml --stage prod

Checklist

• Review the generative AI contribution guidelines
• Adheres to the development guidelines
• Add/update transform tests
  • Using correct values
  • Using wrong values
• Add/update integration tests

Examples?

Please reach out in the comments if you want to add an example. Examples will be
added to sam init through aws/aws-sam-cli-app-templates.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[seshubaws]

Looks like a linting error is causing the tests to fail

[vicheey]

Nit: For the test, shouldn't we use tooling.lambda.aws.dev instead of the variable? So that if we mistakenly modify the CUSTOM_DOMAIN_TOP_LEVEL, the test should be able catch it.

[valerena]

That variable is only used here for the tests and not anywhere in the code. The only purpose is to not have to repeat the full name everywhere, and we can have a single place with the domain that we use for all tests.

[valerena]

Looks like a linting error is causing the tests to fail

fixed!