This gets us a sufficiently-new "stringer" tool that it's able to work
when there are packages in our dependency graph that use Go 1.18 type
parameters.

Without this, we will see the following error the first time we introduce
any dependency that uses type parameters, even if that dependency isn't
involved in our "stringer-ing".
    stringer: Unexpected package creation during export data loading

Backport of docs: Fix condition example into v1.2

Backport of docs: Use more consistent naming in Module Registry Protocol documentation into v1.2

Backport of doc: use american english into v1.2

Merge pull request #31612 from hashicorp/backport/jbardin/static-validate-warnings/initially-steady-rattler

Backport of don't lose warnings from static validation into v1.2

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

v1.2 backport of 31576

We can't validate that data from deprecated nested attributes is used in
the configuration, but we can at least catch the simple case where a
deprecated attribute is referenced directly.

Merge pull request #31603 from hashicorp/backport/jbardin/static-validate-nested-types/possibly-crack-mouse

Backport of Account for `NestedType` in static traversal validation into v1.2

Co-authored-by: Kevin Wang <kwangsan@gmail.com>

Co-authored-by: Kevin Wang <kwangsan@gmail.com>

Backport of update json plan docs with drift output into v1.2

Backport of Add note about module.path and local module sources into v1.2

Merge pull request #31548 from hashicorp/backport/4th-alternate-mirror-directory-fix/closely-key-civet

Backport of Detailing `-chdir` behavior with `terraform.d/plugin` folders into v1.2

Backport of fix grammar: subject-verb agreement into v1.2