Co-authored-by: Nick Fagerlund <nick.fagerlund@gmail.com>

Backport of update go-getter into v1.2

Backport of add unknown paths to diags for debugging into v1.2

Previously we'd discard everything after the second dash.

This also sets an additional variable if it detects that this is an alpha
or development build, which currently does nothing but might eventually
turn on the ability to use experimental features, if we make that
something available only in prereleases.

The actions/checkout workflow does some heroics to try to fetch exactly
the commit being built and nothing else, even if asked to fetch the
history leading up to that commit. That means we don't end up having
enough information to get an accurate answer from "git describe".

Since we're intentionally relying on the git history here, we'll fetch
all of the tags explicitly after initial checkout. Although that does add
some delay to this step, we're intentionally doing this version
calculation only once as a separate workflow job so that all of the other
jobs can still benefit from this action's quicker checkout behavior.

Backport of Add version notes 1.2 into v1.2

Merge pull request #31112 from hashicorp/backport/alisdair/fix-configload-snapshot-panic/forcibly-hopeful-pony

Backport of configs: Fix module loader nil pointer panic into v1.2

54179759 addressed a regression in the
logic for catching when the newer module meta-arguments are used in
conjunction with the legacy practice of including provider configurations
inside modules, where the check started incorrectly catching situations
where the legacy nested provider configuration was in the same module
as the child call using one of those meta-arguments.

This is a regression test to catch if a similar bug arises in the future.

Since it's testing validation rules that apply to an entire configuration
tree, it ended up in a rather idiosyncratic location under the "configload"
package, rather than directly in "configs". The "configs" package only
knows how to load one module at a time, so it's harder to write a test
like this in that context. Due to it being further removed from the code
it is testing, I included a test for the correct error too in order to
increase the chance that we'll learn if future changes in the "configs"
package invalidate this regression test.

I've verified that this new test fails without the change made in the
earlier commit.

Merge pull request #31096 from hashicorp/backport/update-the-non-blockchain-kind-of-crypto/correctly-keen-mutt

Backport of update golang.org/x/crypto again into v1.2

Correct typo in 1.2.0's CHANGELOG.md

Co-authored-by: Katy Moe <katy@katy.moe>

Changing a typo in the Big Fixes list: `inteerruptiong` to `interruption`.

`local-exec` documentation lacks on-destroy documentation

Use different names for var and block

Add warning about drift to cloud block environment variables

Co-authored-by: rita <8647768+ritsok@users.noreply.github.com>

Change private to public in custom conditions example

Co-authored-by: Robin Norwood <rnorwood@hashicorp.com>

Add missing syntax highlighting for terraform snippets

Add swift to workspace docs

Co-authored-by: Laura Pacilio <83350965+laurapacilio@users.noreply.github.com>