Backport of fixed tencentcloud tag into v1.0

[teamterraform]

Backport

This PR is auto-generated from #29445 to be assessed for backporting due to the inclusion of the label 1.0-backport.

WARNING automatic cherry-pick of commits failed. Commits will require human attention.

The below text is copied from the body of the original PR.

---

refer: #29421

This changes only fixed the tencentcloud tag.

I have test it and passed:

go test -v ./...
=== RUN   TestStateFile
=== PAUSE TestStateFile
=== RUN   TestRemoteClient
=== PAUSE TestRemoteClient
=== RUN   TestRemoteClientWithPrefix
=== PAUSE TestRemoteClientWithPrefix
=== RUN   TestRemoteClientWithEncryption
=== PAUSE TestRemoteClientWithEncryption
=== RUN   TestRemoteLocks
=== PAUSE TestRemoteLocks
=== RUN   TestBackend
=== PAUSE TestBackend
=== RUN   TestBackendWithPrefix
=== PAUSE TestBackendWithPrefix
=== RUN   TestBackendWithEncryption
=== PAUSE TestBackendWithEncryption
=== CONT  TestStateFile
=== CONT  TestRemoteLocks
--- PASS: TestStateFile (0.00s)
=== CONT  TestRemoteClientWithPrefix
=== CONT  TestRemoteClient
=== CONT  TestBackendWithPrefix
=== CONT  TestBackendWithEncryption
=== CONT  TestRemoteClientWithEncryption
=== CONT  TestRemoteClient
    backend_test.go:55: TestBackendConfig on *cos.Backend with configs.synthBody{Filename:"<TestWrapConfig>", Values:map[string]cty.Value{"bucket":cty.StringVal("terraform-test-bb31104f27-1"), "key":cty.StringVal("terraform.tfstate"), "prefix":cty.StringVal(""), "region":cty.StringVal("ap-guangzhou")}}
=== CONT  TestRemoteLocks
    backend_test.go:107: TestBackendConfig on *cos.Backend with configs.synthBody{Filename:"<TestWrapConfig>", Values:map[string]cty.Value{"bucket":cty.StringVal("terraform-test-d0add062f4-1"), "key":cty.StringVal("terraform.tfstate"), "prefix":cty.StringVal(""), "region":cty.StringVal("ap-guangzhou")}}
=== CONT  TestBackendWithEncryption
    backend_test.go:170: TestBackendConfig on *cos.Backend with configs.synthBody{Filename:"<TestWrapConfig>", Values:map[string]cty.Value{"bucket":cty.StringVal("terraform-test-ca8180226e-1"), "key":cty.StringVal("terraform.tfstate"), "prefix":cty.StringVal(""), "region":cty.StringVal("ap-guangzhou")}}
=== CONT  TestBackendWithPrefix
    backend_test.go:155: TestBackendConfig on *cos.Backend with configs.synthBody{Filename:"<TestWrapConfig>", Values:map[string]cty.Value{"bucket":cty.StringVal("terraform-test-7397f5929a-1"), "key":cty.StringVal("terraform.tfstate"), "prefix":cty.StringVal("prefix/test"), "region":cty.StringVal("ap-guangzhou")}}
=== CONT  TestRemoteClientWithEncryption
    backend_test.go:90: TestBackendConfig on *cos.Backend with configs.synthBody{Filename:"<TestWrapConfig>", Values:map[string]cty.Value{"bucket":cty.StringVal("terraform-test-2afd24f6e6-1"), "key":cty.StringVal("terraform.tfstate"), "prefix":cty.StringVal(""), "region":cty.StringVal("ap-guangzhou")}}
=== CONT  TestRemoteClientWithPrefix
    backend_test.go:73: TestBackendConfig on *cos.Backend with configs.synthBody{Filename:"<TestWrapConfig>", Values:map[string]cty.Value{"bucket":cty.StringVal("terraform-test-068803fa77-1"), "key":cty.StringVal("terraform.tfstate"), "prefix":cty.StringVal("prefix/test"), "region":cty.StringVal("ap-guangzhou")}}
=== CONT  TestBackend
    backend_test.go:138: TestBackendConfig on *cos.Backend with configs.synthBody{Filename:"<TestWrapConfig>", Values:map[string]cty.Value{"bucket":cty.StringVal("terraform-test-ed1a7d0f02-1"), "key":cty.StringVal("terraform.tfstate"), "prefix":cty.StringVal(""), "region":cty.StringVal("ap-guangzhou")}}
    backend_test.go:141: TestBackendConfig on *cos.Backend with configs.synthBody{Filename:"<TestWrapConfig>", Values:map[string]cty.Value{"bucket":cty.StringVal("terraform-test-ed1a7d0f02-1"), "key":cty.StringVal("terraform.tfstate"), "prefix":cty.StringVal(""), "region":cty.StringVal("ap-guangzhou")}}
--- PASS: TestRemoteClient (1.24s)
=== CONT  TestBackend
    testing.go:299: TestBackend: testing state locking for *cos.Backend
    testing.go:299: TestBackend: testing state locking for *cos.Backend
--- PASS: TestBackend (3.40s)
=== CONT  TestBackendWithPrefix
    backend_test.go:158: TestBackendConfig on *cos.Backend with configs.synthBody{Filename:"<TestWrapConfig>", Values:map[string]cty.Value{"bucket":cty.StringVal("terraform-test-7397f5929a-1"), "key":cty.StringVal("terraform.tfstate"), "prefix":cty.StringVal("prefix/test/"), "region":cty.StringVal("ap-guangzhou")}}
=== CONT  TestBackendWithEncryption
    backend_test.go:173: TestBackendConfig on *cos.Backend with configs.synthBody{Filename:"<TestWrapConfig>", Values:map[string]cty.Value{"bucket":cty.StringVal("terraform-test-ca8180226e-1"), "key":cty.StringVal("terraform.tfstate"), "prefix":cty.StringVal(""), "region":cty.StringVal("ap-guangzhou")}}
--- PASS: TestRemoteClientWithEncryption (5.93s)
--- PASS: TestRemoteClientWithPrefix (6.18s)
=== CONT  TestBackendWithPrefix
    testing.go:299: TestBackend: testing state locking for *cos.Backend
--- PASS: TestRemoteLocks (6.32s)
=== CONT  TestBackendWithEncryption
    testing.go:299: TestBackend: testing state locking for *cos.Backend
--- PASS: TestBackendWithPrefix (7.38s)
--- PASS: TestBackendWithEncryption (8.22s)
PASS
ok      github.com/hashicorp/terraform/internal/backend/remote-state/cos        8.240s

[hashicorp-cla]

)

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement)

Learn more about why HashiCorp requires a CLA and what the CLA includes

---

temp seems not to be a GitHub user.
You need a GitHub account to be able to sign the CLA. If you already have a GitHub account, please add the email address used for this commit to your account.

_{Have you signed the CLA already but the status is still pending? Recheck it).}

[jbardin]

requires manual backport

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