Fix(aws_verifiedaccess_endpoint) load_balancer_options.port not omitted in TCP load balancer

[AKarbas]

Description

The API request for a VA endpoint does not accept LoadBalancerOptions.port when LoadBalancerOptions.protocol="tcp", but it was being set (to 0), breaking creation. This PR makes the inclusion (in the request) conditional.

Relations

Closes #42654

References

• Verified Access User Guide - Create a load balancer endpoint

  (HTTP/HTTPS) For Port, enter the port number. (TCP) For Port ranges, enter a port range and choose Add port.

Output from Acceptance Testing

TODO - WIP
seems broken... will fix later this week.

% make testacc TESTS=TestAccVerifiedAccessEndpoint PKG=ec2
make: Verifying source code with gofmt...
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go1.23.9 test ./internal/service/ec2/... -v -count 1 -parallel 20 -run='TestAccVerifiedAccessEndpoint'  -timeout 360m -vet=off
2025/05/20 16:36:24 Initializing Terraform AWS Provider...
testing: warning: no tests to run
PASS
ok  	github.com/hashicorp/terraform-provider-aws/internal/service/ec2	4.121s [no tests to run]
...

[github-actions]

Community Guidelines

This comment is added to every new Pull Request to provide quick reference to how the Terraform AWS Provider is maintained. Please review the information below, and thank you for contributing to the community that keeps the provider thriving! 🚀

Voting for Prioritization

• Please vote on this Pull Request by adding a 👍 reaction to the original post to help the community and maintainers prioritize it.
• Please see our prioritization guide for additional information on how the maintainers handle prioritization.
• Please do not leave +1 or other comments that do not add relevant new information or questions; they generate extra noise for others following the Pull Request and do not help prioritize the request.

Pull Request Authors

• Review the contribution guide relating to the type of change you are making to ensure all of the necessary steps have been taken.
• Whether or not the branch has been rebased will not impact prioritization, but doing so is always a welcome surprise.