feat: Add S3 endpoint dns_entry output

[tx-kstav]

Description

Add output for dns_entry of S3 endpoint.

Motivation and Context

I was missing the output for my use case.

Breaking Changes

I have not found anything broken. It is a simple addition in outputs, it should not break anything.

How Has This Been Tested?

• I have tested and validated these changes using one or more of the provided examples/* projects
• I have tested the change against my own VPC. The output is correctly shown as shown below (details omitted), and I can use it in other resources in my Terragrunt code, as a dependency.

vpc_endpoint_s3_dns_entry = [
  {
    "dns_name" = "*.vpce-XXX-YYY.s3.eu-west-1.vpce.amazonaws.com"
    "hosted_zone_id" = "ZZZ"
  },
  {
    "dns_name" = "*.vpce-XXX-YYY-eu-west-1b.s3.eu-west-1.vpce.amazonaws.com"
    "hosted_zone_id" = "ZZZ"
  },
  {
    "dns_name" = "*.vpce-XXX-YYY-eu-west-1a.s3.eu-west-1.vpce.amazonaws.com"
    "hosted_zone_id" = "ZZZ"
  },
  {
    "dns_name" = "*.vpce-XXX-YYY-eu-west-1c.s3.eu-west-1.vpce.amazonaws.com"
    "hosted_zone_id" = "ZZZ"
  },
]

Thank you.

[tx-kstav]

@bryantbiggs should i close this and wait for #635 ?

[bryantbiggs]

thanks for the PR @tx-kstav ! I think #635 will be the direction so that endpoint management is more scalable for the module but lets wait and see. I will add this PR to the list of issues/PRs closed by that PR so that if it does go through, things will get cleaned up. its ok to leave open for now

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.