Add multi_party_conference_enabled to aws_connect_instance

[schuylr]

Description

Add the multi_party_conference_enabled argument to the aws_connect_instance resource, as well as the multi_party_conference_enabled attribute to the same data source.

Relations

Closes #27728

References

https://docs.aws.amazon.com/connect/latest/adminguide/multi-party-calls.html
https://docs.aws.amazon.com/connect/latest/APIReference/API_UpdateInstanceAttribute.html

Output from Acceptance Testing

terraform-provider-aws % make testacc TESTARGS='-run=TestAccConnect_serial/Instance/basic' PKG=connect
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/connect/... -v -count 1 -parallel 20  -run=TestAccConnect_serial/Instance/basic -timeout 180m
=== RUN   TestAccConnect_serial
=== RUN   TestAccConnect_serial/Instance
=== RUN   TestAccConnect_serial/Instance/basic
=== RUN   TestAccConnect_serial/Instance/dataSource_basic
=== RUN   TestAccConnect_serial/InstanceStorageConfig
=== RUN   TestAccConnect_serial/InstanceStorageConfig/basic
--- PASS: TestAccConnect_serial (328.13s)
    --- PASS: TestAccConnect_serial/Instance (234.96s)
        --- PASS: TestAccConnect_serial/Instance/basic (110.64s)
        --- PASS: TestAccConnect_serial/Instance/dataSource_basic (124.32s)
    --- PASS: TestAccConnect_serial/InstanceStorageConfig (93.17s)
        --- PASS: TestAccConnect_serial/InstanceStorageConfig/basic (93.16s)
PASS
ok  	github.com/hashicorp/terraform-provider-aws/internal/service/connect	332.470s

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this pull request by adding a 👍 reaction to the original post to help the community and maintainers prioritize this pull request.
• Please see our prioritization guide for information on how we prioritize.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

For Submitters

• Review the contribution guide relating to the type of change you are making to ensure all of the necessary steps have been taken.
• For new resources and data sources, use skaff to generate scaffolding with comments detailing common expectations.
• Whether or not the branch has been rebased will not impact prioritization, but doing so is always a welcome surprise.

[sasidhar-aws]

Looks good to me.

[ewbankkit]

LGTM 🚀.

% make testacc TESTARGS='-run=TestAccConnect_serial/Instance/basic' PKG=connect
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/connect/... -v -count 1 -parallel 20  -run=TestAccConnect_serial/Instance/basic -timeout 180m
=== RUN   TestAccConnect_serial
=== RUN   TestAccConnect_serial/Instance
=== RUN   TestAccConnect_serial/Instance/basic
=== RUN   TestAccConnect_serial/Instance/dataSource_basic
=== RUN   TestAccConnect_serial/InstanceStorageConfig
=== RUN   TestAccConnect_serial/InstanceStorageConfig/basic
--- PASS: TestAccConnect_serial (320.27s)
    --- PASS: TestAccConnect_serial/Instance (231.07s)
        --- PASS: TestAccConnect_serial/Instance/basic (106.46s)
        --- PASS: TestAccConnect_serial/Instance/dataSource_basic (124.61s)
    --- PASS: TestAccConnect_serial/InstanceStorageConfig (89.20s)
        --- PASS: TestAccConnect_serial/InstanceStorageConfig/basic (89.20s)
PASS
ok  	github.com/hashicorp/terraform-provider-aws/internal/service/connect	324.742s

[ewbankkit]

@schuylr Thanks for the contribution 🎉 👏.

[github-actions]

This functionality has been released in v4.40.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

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