feat: Add support for multiple services inside service_connect_configuration

[saki-engineering]

Description

Add support for multiple services inside service_connect_configuration

Motivation and Context

According to the Documentation of ECS, service_connect_configuration can configure multiple client-server services and hashicorp/aws provider supports for deploying it (as far as I know) after the major version 5.

• Closes feat: Add support for multiple service inside service_connect_configuration #163

service_connect_configuration supports the following:

• enabled - (Required) Specifies whether to use Service Connect with this service.
• log_configuration - (Optional) The log configuration for the container. See below.
• namespace - (Optional) The namespace name or ARN of the aws_service_discovery_http_namespace for use with Service Connect.
• service - (Optional) The list of Service Connect service objects. See below.

Quote: https://registry.terraform.io/providers/hashicorp/aws/5.0.0/docs/resources/ecs_service#service_connect_configuration

However this module does not accept the list of Service Connect service objects and that is the issue this PR wants to fix.

Breaking Changes

Yes. Existing examples/* cannot plan/apply if this PR is merged.

How Has This Been Tested?

• I have updated at least one of the examples/* to demonstrate and validate my change(s)
• I have tested and validated these changes using one or more of the provided examples/* projects

• I have executed pre-commit run -a on my pull request

[bryantbiggs]

ah shoot - yes, you are correct. the change looks great and is valid, but it is a breaking change. Lets hold on this for the next breaking change

[github-actions]

This PR has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this PR will be closed in 10 days

[bryantbiggs]

bad bot

[bryantbiggs]

Thank you! Merging into the wip/v6 branch

[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.