Emit QueryCountMetrics for SQL Queries

[jtuglu-netflix]

Fixes #11652.

Description

This pulls out the query count metrics logic from QueryResource and places it into BaseQueryCounterResource, which allows for SqlResource to share this codepath. An alternative approach is here, which avoids shared logic between the two resources. As stated in the issue, the ideal change would be to have SqlResource inherit, or simply pass on, all query handling to QueryResource, but that seemed a bit out of scope for this PR (but I can do this).

Notes:

• I removed the get/increment handles from both QueryResource and SqlResource for simplicity, and simply made the counter package-private for accessing in tests. I can add the get() accessors back if necessary.

Release note

---

Key changed/added classes in this PR

• extensions-core/multi-stage-query/src/main/java/org/apache/druid/msq/dart/controller/http/DartSqlResource.java
• extensions-core/multi-stage-query/src/test/java/org/apache/druid/msq/dart/controller/http/DartSqlResourceTest.java
• quidem-ut/src/main/java/org/apache/druid/quidem/ExposedAsBrokerQueryComponentSupplierWrapper.java
• server/src/main/java/org/apache/druid/server/BaseQueryCountResource.java
• server/src/main/java/org/apache/druid/server/BrokerQueryResource.java
• server/src/main/java/org/apache/druid/server/QueryMetricCounter.java
• server/src/main/java/org/apache/druid/server/QueryResource.java
• server/src/main/java/org/apache/druid/server/QueryResultPusher.java
• server/src/test/java/org/apache/druid/server/QueryResourceTest.java
• server/src/test/java/org/apache/druid/server/QueryResultPusherTest.java
• services/src/main/java/org/apache/druid/cli/CliBroker.java
• services/src/main/java/org/apache/druid/cli/CliHistorical.java
• services/src/main/java/org/apache/druid/guice/QueryablePeonModule.java
• sql/src/main/java/org/apache/druid/sql/http/SqlResource.java
• sql/src/test/java/org/apache/druid/sql/http/SqlResourceTest.java

---

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.