This will report the names of flaky tests instead of just counting them.

consul/connect: Enable running multiple ingress gateways per Nomad agent

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

Fixed Markdown for GCP example.

Connect ingress gateway services were being registered into Consul without
an explicit deterministic service ID. Consul would generate one automatically,
but then Nomad would have no way to register a second gateway on the same agent
as it would not supply 'proxy-id' during envoy bootstrap.

Set the ServiceID for gateways, and supply 'proxy-id' when doing envoy bootstrap.

Fixes #9834

consul/connect: always set gateway proxy default timeout

If the connect.proxy stanza is left unset, the connection timeout
value is not set but is assumed to be, and may cause a non-fatal NPE
on job submission.

This has to have been unused because the HasPrefix operation is
backwards, meaning a Command.Env that includes PATH= never would have
worked; the default path was always used.

* Persist shared allocated ports for inplace update

Ports were not copied over when performing inplace updates in the
generic scheduler

* changelog

* drop spew

Missed improvement regarding IGW task customization