Backport of Bump go-getter v1.8.2 into v1.13

[github-actions]

Backport

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

🚨

Warning automatic cherry-pick of commits failed. If the first commit failed,
you will see a blank no-op commit below. If at least one commit succeeded, you
will see the cherry-picked commits up to, not including, the commit where
the merge conflict occurred.

The person who merged in the original PR is:
@YakDriver
This person should resolve the merge-conflict(s) by either:

• Manually completing the cherry picks into this branch
• Creating a new branch and manually cherry-picking all commits being backported

merge conflict error: POST https://api.github.com/repos/hashicorp/terraform/merges: 409 Merge conflict []

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

---

tl;dr: We want AWS non-standard partition support plus security improvements without impacting Windows support.

The main point was for Terraform via go-getter to support work in AWS partitions besides aws, such as GovCloud, China, isolated, and custom partitions. That was achieved in go-getter v1.8.0, which also modernized code and moved off unsupported aws-sdk-go v1.

However, go-getter v1.8.0, via modern Go (1.23+), also introduced problems with Windows junction points. To fix this, go-getter v1.8.1 added comprehensive symlink resolution with Windows junction point support. Now, v1.8.2 fixes an issue on Windows with temporary directories.

Related:

• bump: go-getter to 1.8.0 #37567
• Upgrade to aws-sdk-go-v2, v1 is unsupported go-getter#548
• [fix] Windows junction handling go-getter#557
• Ensure temporary directory symlinks do not cause errors go-getter#560

Target Release

1.15.x

Rollback Plan

• If a change needs to be reverted, we will roll out an update to the code within 7 days.

Changes to Security Controls

Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.

CHANGELOG entry

• This change is user-facing and I added a changelog entry.
• This change is not user-facing.

---

Overview of commits

• edb3f64

[hashicorp-cla-app]

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 have already 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.}

[hashicorp-cla-app]

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 have already 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.}

[SarahFrench]

Given the backport failed I'll close this and make a new PR