• Attach user identity to router request logs

• Add test

• More tests

(cherry picked from commit 7802078)

Description

Currently, with the Druid version we are using, the user information is missing in the logs when a user queries a data source the via Druid Console e.g.

{"query/time":212,"success":true}	{"query":"SELECT \"__time\", \"logical_cluster_id\", \"value_max\"\nFROM \"telemetry_metrics\"\nWHERE \"name\" = 'cc_control_plane_kafka.requested_ckus' and  \"value_max\" > 0\n\n","context":{"sqlOuterLimit":1001,"sqlQueryId":"41636992-128d-42c0-92a9-6432dd2f58e4","queryId":"41636992-128d-42c0-92a9-6432dd2f58e4"}}

The user information is required as a part of the ongoing Audit Logging Effort.

The OpenSource branch has the change to include user identity in the request logs PR. Cherry-picked the same to include the change.

This PR has:

• been self-reviewed.
  • using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)
• added documentation for new or modified features or behaviors.
• a release note entry in the PR description.
• added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
• added or updated version, license, or notice information in licenses.yaml
• added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
• added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
• added integration tests.
• been tested in a test Druid cluster.