enable -race detector for testing api

Fix the broken link in the bootstrapping custom scheduler warning

consul: plumbing for specifying consul namespace in job/group

Co-authored-by: Tim Gross <tgross@hashicorp.com>

This PR adds the common OSS changes for adding support for Consul Namespaces,
which is going to be a Nomad Enterprise feature. There is no new functionality
provided by this changeset and hopefully no new bugs.

* changelog entry for on_update configuration settings

* Update CHANGELOG.md
Co-authored-by: Tim Gross <tgross@hashicorp.com>
Co-authored-by: Tim Gross <tgross@hashicorp.com>

chore: bump golangci-lint from v1.24 to v1.39

Signed-off-by: Yoan Blanc <yoan@dosimple.ch>

Signed-off-by: Yoan Blanc <yoan@dosimple.ch>

Signed-off-by: Yoan Blanc <yoan@dosimple.ch>

docs: specify buf v0.30.1

If you use too new of a `buf` you will hit #10293

Memory stats for cgroup-v2

When a volume is registered via `nomad volume register` and not via the
creation workflow, it may not have any of the capacity fields set (as they're
not used for registration). Handle this case without error, and let the
downstream RPCs handle the error case for `nomad volume create`.

move json handle back to `structs`

this was unecessary after refactoring, so this moves them back to their
original location in package structs

dev: ignore msgpack codegen code in dev by default

If a task doesn't report RSS, let's use memory usage.

remove deprecated `Drain` field from `structs.Node`

This change disables using msgpack generated serializers in dev by
default.

In released binaries, we use code-generated msgpack serializers to
improve performance.  However, in development, code generated
serializers are a pain. If a developer forgets to re-generate code, the
code generated gets out of sync with the go structs, and result into
subtle bugs where some values appear not to persist as expected.

The CI and release scripts will continue to use the msgpack
code-generation. Devs who want to test locally can set
`GO_TAGS=codegen_generated` as well.

docs: add fixed-value and pass-through autoscaler plugin docs.

docs: Update AWS permission requirements for the Autoscaler

docs: add Autoscaler CLI flags for policy eval configuration

In order to support new node RPCs, we need to fingerprint plugin capabilities
in more detail. This changeset mirrors recent work to fingerprint controller
capabilities, but is not yet in use by any Nomad RPC.

This adds UI support for receiving the one-time token passed via query parameter, as in #10134
and related PRs, and exchanging it for its corresponding secret ID. When this works, it’s mostly
invisible, with a brief flash of the OTT onscreen.

The authentication failure message now suggests the -authenticate flag.

When OTT exchange fails, it shows a whole-page error.

This includes a known UX shortcoming in that the OTT will not disappear from the URL when an
identifier is specified on the command line, like nomad ui -authenticate jobname. The goal is to
address that shortcoming in a forthcoming pull request.

If the docker engine is running on cgroup-v2 host, then RSS and Max
Usage doesn't get reported.

Using a heauristic here to avoid adding more API calls to the Docker
Engine to infer cgroups version. Also, opted to avoid coordinating stats
collection with fingerprinting, which adds concurrency complexities.

If the host is running with cgroup-v2, RSS and Max Usage doesn't get
reported anymore.