* Add explicit `ReadTimeout` for ConsulConfigurationWatcher

* Bump up skywalking-eyes

Support HTTP APIs list:

- /api/v1/metadata
- /api/v1/labels
- /api/v1/label/{label_name}/values
- /api/v1/series
- /api/v1/query
-/api/v1/query_range

Support basic promQL for query traffic/metrics/labeled_metrics/topN/sampled_records from OAP

* Remove TLS support from firehose receiver

Notice, no HTTPS/TLS setup support. By following AWS Firehose request, it uses [proxy request](https://en.wikipedia.org/wiki/Proxy_server#Web_proxy_servers) (`https://...` instead of `/aws/firehose/metrics`), there must be a proxy(Nginx, Envoy, etc.).

* Update docs.

- `./mvnw test ...` by its nature only runs unit tests, whose name is pattern of `*Test`, and it does never runs integration tests, whose name is patter of `IT*` or `*IT`, so in this PR we use `./mvnw clean test ...` to only run unit tests.
- `./mvnw integration-test ...` will run integration tests and unit tests, so we have `skipUTs` to control whether to skip the UT when running ITs, we already had this before.
  - As for ITs, we have two groups, one is normal tests without any `@Tag`s, the other one is slow integration tests, which is annotated with `@Tag("slow")`, so we divided the integration tests into two workflow jobs:
  - `./mvnw -DskipUTs=true clean integration-test -DexcludedGroups=slow ...` run the ITs but don't run the slow ITs and UTs, `-DexcludedGroups=slow` excludes tests annotated with `@Tag("slow")`
  - `./mvnw -DskipUTs=true clean integration-test -Dcheckstyle.skip -Dtest=${{ matrix.test.class }}` run the slow ITs (because `excludedGroups` is not set) one case at a time, by setting `-Dtest={{ class }}`, not run UTs,

* Swap `Column#name` and `ElasticSearch.Column#columnAlias`
* Rename `ElasticSearch.Column#columnAlias` to `ElasticSearch.Column#legacyName`

The previous implementation could only support scopes being catalogs.

Add aws-firehose-receiver to support collecting AWS CloudWatch metric(OpenTelemetry format) (#10300)

* Add missing FastAPI logo
* Update the log details page to support the formatted display of JSON content