add listTag condition to allow for failed sagemaker app

[bruceadowns]

Description

Add a condition to the listing of tags for a SageMaker App. If a SageMaker App is in a failed state due to a startup failure (i.e. lifecycle script) terraform (and aws cli) is unable to list tags and the action will continue to fail until the app is manually cleaned up.

Here's the error that cannot be overcome:

│ Error: listing tags for SageMaker App (arn:aws:sagemaker:us-west-2:167806804118:app/d-feb4mgoibnna/default-user/jupyterserver/default): operation error SageMaker: ListTags, https response error StatusCode: 400, RequestID: b844e0b2-e840-434b-ba72-453449e7292e, api error ValidationException: UnknownError
│ 
│   with module.studio_domain[0].aws_sagemaker_app.user_default["sagemaker-amps-c-uw2-foo.default-user"],
│   on modules/studio/main.tf line 80, in resource "aws_sagemaker_app" "user_default":
│   80: resource "aws_sagemaker_app" "user_default" {

This occurs when the SageMaker App fails to startup, and is not cleared for 24h.

Relations

Closes #0000

References

Output from Acceptance Testing

$ make test
make: Verifying source code with gofmt...
==> Checking that code complies with gofmt requirements...
make: Running unit tests...
go1.23.2 test -count 1 ./...  -timeout=15m
?       github.com/hashicorp/terraform-provider-aws     [no test files]
?       github.com/hashicorp/terraform-provider-aws/internal/acctest/generate   [no test files]
...
ok      github.com/hashicorp/terraform-provider-aws/internal/verify     0.490s
ok      github.com/hashicorp/terraform-provider-aws/names       0.645s

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