s/mananger/manager/g

drivers/docker: rename logging `type` to `driver`

Docker uses the term logging `driver` in its public documentations: in
`docker` daemon config[1], `docker run` arguments [2] and in docker compose file[3].
Interestingly, docker used `type` in its API [4] instead of everywhere
else.

It's unfortunate that Nomad used `type` modeling after the Docker API
rather than the user facing documents.  Nomad using `type` feels very
non-user friendly as it's disconnected from how Docker markets the flag
and shows internal representation instead.

Here, we rectify the situation by introducing `driver` field and
prefering it over `type` in logging.

[1] https://docs.docker.com/config/containers/logging/configure/
[2] https://docs.docker.com/engine/reference/run/#logging-drivers---log-driver
[3] https://docs.docker.com/compose/compose-file/#logging
[4] https://docs.docker.com/engine/api/v1.39/#operation/ContainerCreate

tests: disable upgrade e2e tests

* update formatting and add toJSON function with explanation

* edit typo

* Update website/source/guides/operations/vault-integration/index.html.md
Co-Authored-By: Omar-Khawaja <Omar-Khawaja@users.noreply.github.com>

* fixing clarification bullet explaining the use of toJSON

Upgrade e2e tests are failing and we haven't had bandwith to fix yet.
Having them fail makes it easy for us to miss other failures and
regressions.

As such, skip the upgrade e2e tests until we fix them.

On Windows, Nomad only supports Windows containers, so report as
unhealthy otherwise.

logmon fixes

Other logmon tests should be portable.

Port some integration tests of driver fingerprinting.

Some tests (e.g. `TestFingerprintManager_Run_DriversInBlacklist`) have
been subsituted by more isolated tests in
`client/pluginmanager/drivermanager/manager_test.go`

docker: Support Stats on Windows

This code chooses to be conservative as opposed to optimal: when failing
to reattach to logmon simply return a recoverable error instead of
immediately trying to restart logmon.

The recoverable error will cause the task's restart policy to be
applied and a new logmon will be launched upon restart.

Trying to do the optimal approach of simply starting a new logmon
requires error string comparison and should be tested against a task
actively logging to assert the behavior (are writes blocked? dropped?).

More alloc runner tests ported from 0.8.7

docker: Return undetected before first detection

This commit causes the docker driver to return undetected before it
first establishes a connection to the docker daemon.

This fixes a bug where hosts without docker installed would return as
unhealthy, rather than undetected.

Port some 0.8.7 alloc runner tests

Created .github; Added CoC

Set NextEval when making `failed-follow-up` evals

When Vault token expires and task is restarted, emit `TaskRestartSignal`
similar to v0.8.7

From https://github.com/hashicorp/nomad/blob/v0.8.7/client/task_runner_test.go#L1427

From https://github.com/hashicorp/nomad/blob/v0.8.7/client/task_runner_test.go#L1352

From https://github.com/hashicorp/nomad/blob/v0.8.7/client/task_runner_test.go#L620

From https://github.com/hashicorp/nomad/blob/v0.8.7/client/task_runner_test.go#L1275

From https://github.com/hashicorp/nomad/blob/v0.8.7/client/task_runner_test.go#L1195

Port TestAllocRunner_RetryArtifact from https://github.com/hashicorp/nomad/blob/v0.8.7/client/alloc_runner_test.go#L610-L672

I changed the test name because it doesn't actually test that artifact
hooks is retried

Support json logging for CLI output for agent