feat: Add json-file log driver

[aaithal]

feat: Add json-file log driver

Overview

This PR adds a json-file log driver to the shim-logger, wrapping moby's
upstream jsonfilelog
behind the same driver pattern that awslogs, fluentd, and splunk use today.

The driver writes container stdout/stderr to a host file in the
Docker JSON-file format — one JSON object per line, e.g.:

{"log":"hello\n","stream":"stdout","time":"2026-05-27T21:07:48.123456789Z"}

It supports moby's max-size, max-file, compress, tag, labels,
labels-regex, env, and env-regex options unchanged, plus a required
--log-path for the per-container output file.

Usage

shim-loggers-for-containerd \
  --log-driver json-file \
  --log-path <abs-path-to-output-file> \
  [--max-size 10m] \
  [--max-file 5] \
  [--compress true] \
  [--json-file-tag '{{.ImageName}}/{{.ID}}'] \
  [--json-file-labels foo,bar] \
  [--json-file-labels-regex '^app\..*'] \
  [--json-file-env KEY1,KEY2] \
  [--json-file-env-regex '^APP_.*']

Changes Made

• New driver package logger/jsonfile — wraps moby's jsonfilelog.New,
  honoring the existing NonBlockingMode wrapping pattern when buffered mode
  is requested. Optional fields are only added to the moby config map when
  non-empty so moby's ValidateLogOpts does not reject stray empty values.

• New common option logger.WithLogPath — sets info.LogPath on the
  logger.Info struct moby's jsonfilelog.New reads to derive the output
  filename. The shim does not create the directory; the caller
  (containerd / agent) is responsible for precreating it with the right
  ownership and mode.

• Wiring through init.go / args.go / main.go — registers all 9
  flags, adds getJSONFileArgs() (returns an error if --log-path is unset),
  and dispatches case jsonfile.DriverName to runJSONFileDriver. Adds
  json-file to the --log-driver help text.

• Prefixed input flag names for the 5 options that collide with other
  drivers: --json-file-tag, --json-file-labels, --json-file-labels-regex,
  --json-file-env, --json-file-env-regex. Same convention splunk and
  fluentd already use — shim-logger's pflag namespace is flat across drivers.
  The flags are forwarded to moby under their bare names (tag, labels,
  labels-regex, env, env-regex).

• compress defaults to "do not set" — moby rejects compress=true
  unless max-file >= 2 and max-size is set, so making it opt-in keeps a
  partial config from becoming a hard failure.

Drive-by: relax heap threshold for TestMemoryScenario_LargeLines_NonBlocking_DefaultBuffer

Commit 3 of this PR (26c2185) is unrelated to the json-file work. The
test added in #391 uses a 210 MiB threshold derived from a 160 MiB baseline
plus a 30% race-instrumentation buffer; in practice the OS allocator and Go
version each add their own jitter on top of -race, so Windows + Go 1.24

• race observes ~225 MiB and trips the check on this PR's CI run (Linux +
  Go 1.24 + race observes 188.8 MiB). Bumped to 256 MiB (1.6× the 160 MiB
  baseline) — a real regression doubling the working set would still trip.

Happy to drop this commit and split into a separate PR if maintainers
prefer; calling it out so it's visible.

Testing

Unit tests — make test-unit passes across all packages:

• logger/jsonfile/logger_test.go covers config translation, empty-args →
  empty config map, TagSpecified=false suppression, and the
  validate-keys-not-values contract of moby's ValidateLogOpts.
• args_test.go adds TestGetJSONFileArgs covering the --log-path-required
  error path, log-path-only defaults, and the full options pass-through.

E2E tests — make test-e2e-for-json-file runs 6 specs against a
local containerd, all pass:

Spec	Verifies
envelope format	every line is {"log":...,"stream":"stdout","time":"<RFC3339Nano>"}
--max-size rotation	enough output forces 2–3 rotated files
--max-file cap	over-rotation is bounded by the cap
no-rotation below --max-size	a single small printf produces 1 file
file mode	active file has mode 0640 (moby's hardcoded value)
--log-path required	missing flag fails the container task fast

Two e2e infra additions: e2e/common.go grows a SendCommandByContainerd
helper (the existing SendTestLogByContainerd delegates to it) so specs
can run arbitrary shell commands when they need to control payload shape;
--log-path is resolved to an absolute path at suite-build time because
the shim-logger inherits its CWD from containerd, not from the test
runner. Comment in the test file explains the latter.

---

By submitting this pull request, I confirm that you can use, modify, copy,
and redistribute this contribution, under the terms of your choice.

[JoseVillalta]

non-blocking minor comments.

[JoseVillalta]

LGTM