Implement Hotspot detection in Go Collector

[empiredan]

This issue will track the implementation of hotspot detection in the Go collector. Since one of the goals of the Go collector is to replace the CPP-based collector, it needs to cover all hotspot detection capabilities provided by the CPP implementation, including following features:

1. Periodically collect and aggregate read/write traffic metrics to detect whether hotspots exist on each partition of each table.
2. create and update the corresponding queryable metric data for hot partitions.
3. Support sending requests to the detected hotspot partitions to query hotspot keys, to collect statistics on the current abnormal hotspot traffic.

For more details on hotspot detection, please refer to the documentation.

Task list:

• feat(collector): introduce the hotspot detector into go-collector #1943
• feat(collector): Go Collector fetches and aggregates hotspot-related metrics #2357
• feat(collector): calculate the total statistics for both reads and writes and record them as history for analysis of hotspot partitions #2359
• feat(go-client): introduce Equal APIs for HostPort and RPCAddress #2360
• feat(collector): analyze statistics to determine whether partitions are hotspots #2367
• feat(collector): clean up expired tables during hotspot detection #2369
• feat(collector): support reading config file path from CLI and loading log configuration from config file in Go Collector #2375