Noticed this error in some production logs, and they were far from
helpful. Changes:

1. Include job ID in logs
2. Wrap errors and log once instead of double log lines
3. Test fsm error handling behavior

consul/connect: make use of task kind to determine service name in consul token checks

This changeset is the OSS hooks for what will be implemented in ENT.

When consul.allow_unauthenticated is set to false, the job_endpoint hook validates
that a `-consul-token` is provided and validates the token against the privileges
inherent to a Consul Service Identity policy for all the Connect enabled services
defined in the job.

Before, the check was assuming the service was of type sidecar-proxy. This fixes the
check to use the type of the task so we can distinguish between the different connect
types.

fix changelog entry placement

resolve prefix bugs around job scaling policies

consul/connect: add initial support for ingress gateways

Respect alloc job version for lost/failed allocs

Co-authored-by: Chris Baker <1675087+cgbaker@users.noreply.github.com>

`(alloc.DeploymentStatus == nil || !alloc.DeploymentStatus.IsCanary())`
and `!alloc.DeploymentStatus.IsCanary()` are equivalent.

To address review comments

Assorted small fixes

Fix Broken Learn Guide Links in Security Model

remove preemption, add cross-namespace queries

This continues #8455 by adding accessibility audits to component integration
tests and fixing associated errors. It adds audits to existing tests rather than
adding separate ones to facilitate auditing the various permutations a
component’s rendering can go through.

It also adds linting to ensure audits happen in component tests. This
necessitated consolidating test files that were scattered.

changelog entry for enterprise bug

remove preemption from summary of governance and policy module since it is now OSS.
add cross-namespace queries to that same sentence.

- fix panic in serializing nil allocs in volume API
- prevent potential panic in serializing plugin allocs

Clarify how to handle prefix value and path traversal within the alloc
dir but outside the prefix directory.

Fixes a bug where `keys` metadata wasn't populated, as we iterated over
the empty newly-created `keys` map rather than the request Meta field.

Apparently `\` followed by a digit number can cause hcl parser to panic!
Will fix in hcl library, but using a hammer to squash any similar issue
here.

Ensure that d.mu is only dereferenced if d is not-nil, to avoid a null
dereference panic.

remove local SECURITY.md in favor of org-wide policy