agent-platform release v4.143.0

The data plane’s access log carries the request id: request_id (giantswarm/agent-platform#867). The <release>-access-log policy adds the x-request-id request header as request_id to every access log line, beside agent_instance_id. The Dev Portal’s backend sets that header on every call it makes through the data plane and names it in an error banner, so the banner’s id finds the gateway line of the failing call. The data plane generates no id: a request without the header logs none. The connectivity README’s “Access log attributes” lists the chart’s field set. make verify-access-log asserts both default fields. Every installation with the agentgateway data plane gets one more field on its access log; no pod rolls.