* remove website source code and related circle jobs

* remove data files

* updates platform-cli

* update local instructions

* updates package-lock

This pull request was automerged via backport-assistant

This pull request was automerged via backport-assistant

This pull request was automerged via backport-assistant

This pull request was automerged via backport-assistant

This pull request was automerged via backport-assistant

This pull request was automerged via backport-assistant

* Merge pull request #11889 from hashicorp/build-update-circle

build: upgrade circleci configuration

* Merge pull request #12299 from hashicorp/ci-parallel

ci: trade test parallelization for unconstrained gomaxprocs

* Merge pull request #12321 from hashicorp/ci-less-logging

ci: limit gotestsum to circle ci

* CI: build binaries for UI branches (#12594)

Build binaries for every code change, not just backend code
changes. This means that we'll have up-to-date compiled assets for
every commit available in CircleCI artifacts.

* cgutil test: reserve only a single CPU for AddAlloc test

Reserving the entire machine's worth of CPUs for the `AddAlloc` test
triggers a condition where the empty shared CPUs defaults to the
parent CPU set on some system configurations. This was done in `main`
as part of cgroups v2 work, but we need to backport this to earlier
branches in order to use the same machines across branches.
Co-authored-by: Seth Hoenig <seth.a.hoenig@gmail.com>
Co-authored-by: Tim Gross <tgross@hashicorp.com>

This pull request was automerged via backport-assistant

This pull request was automerged via backport-assistant

Merge pull request #12754 from hashicorp/backport/b-csi-plugin-after-client-restart/purely-arriving-mite

This pull request was automerged via backport-assistant

The Prestart hook for task runner hooks doesn't get called when we
restore a task, because the task is already running. The Postrun hook
for CSI plugin supervisors needs the socket path to have been
populated so that the client has a valid path.
Co-authored-by: Tim Gross <tgross@hashicorp.com>

This pull request was automerged via backport-assistant

This pull request was automerged via backport-assistant

This pull request was automerged via backport-assistant

This pull request was automerged via backport-assistant

The plugin manager for CSI hands out instances of a plugin for callers
that need to mount a volume. The `MounterForPlugin` method accesses
the internal instances map without a lock, and can be called
concurrently from outside the plugin manager's main run-loop.

The original commit for the instances map included a warning that it
needed to be accessed only from the main loop but that comment was
unfortunately ignored shortly thereafter, so this bug has existed in
the code for a couple years without being detected until we ran tests
with `-race` in #12098. Lesson learned here: comments make for lousy
enforcement of invariants!

The volume watcher design was based on deploymentwatcher and drainer,
but has an important difference: we don't want to maintain a goroutine
for the lifetime of the volume. So we stop the volumewatcher goroutine
for a volume when that volume has no more claims to free. But the
shutdown races with updates on the parent goroutine, and it's possible
to drop updates. Fortunately these updates are picked up on the next
core GC job, but we're most likely to hit this race when we're
replacing an allocation and that's the time we least want to wait.

Wait until the volume has "settled" before stopping this goroutine so
that the race between shutdown and the parent goroutine sending on
`<-updateCh` is pushed to after the window we most care about quick
freeing of claims.

* Fixes a resource leak when volumewatchers are no longer needed. The
  volume is nil and can't ever be started again, so the volume's
  `watcher` should be removed from the top-level `Watcher`.

* De-flakes the GC job test: the test throws an error because the
  claimed node doesn't exist and is unreachable. This flaked instead of
  failed because we didn't correctly wait for the first pass through the
  volumewatcher.

  Make the GC job wait for the volumewatcher to reach the quiescent
  timeout window state before running the GC eval under test, so that
  we're sure the GC job's work isn't being picked up by processing one
  of the earlier claims. Update the claims used so that we're sure the
  GC pass won't hit a node unpublish error.

* Adds trace logging to unpublish operations

This pull request was automerged via backport-assistant

The client configuration options for drivers have been deprecated
since 0.9. We haven't torn them out completely but because they're
deprecated it's been hard to guarantee correct behavior. Remove the
documentation so that users aren't misled about their viability.