Inconsistent `aws configure` behavior involving Windows environment variable

### Describe the bug

In the [SDKs & Tools Reference Guide](https://docs.aws.amazon.com/sdkref/latest/guide/file-location.html), it mentions that all platforms first check the `HOME` environment variable for the config and credentials files.

But in the CLI [configuration documentation](https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-files.html#cli-configure-files-where) it notes:

>The AWS CLI stores sensitive credential information that you specify with `aws configure` in a local file named credentials, in a folder named `.aws` in your home directory. The less sensitive configuration options that you specify with `aws configure` are stored in a local file named `config`, also stored in the `.aws` folder in your home directory.
>
>Where you find your home directory location varies based on the operating system, but is referred to using the environment variables `%UserProfile%` in Windows and `$HOME` or `~` (tilde) in Unix-based systems.

We need to confirm:
- If all SDKs first look for the `HOME` environment variable in Windows environments.
- If `aws configure` should be updated to update the `HOME` environment variable in Windows.
- If SDK/CLI documentation should be updated to clarify this behavior.

Originally reported here: https://github.com/aws/aws-cli/discussions/7035

Related Go PR: https://github.com/aws/aws-sdk-go/pull/1308