build(deps): use hashicorp/go-metrics instead of armon/go-metrics (backport #16790) (#16800)

Co-authored-by: Julien Robert <julien@rbrt.fr>

docs/architecture/adr-013-metrics.md

@@ -21,7 +21,7 @@ and is rich with ecosystem tooling.
 
 We must also aim to integrate metrics into the Cosmos SDK in the most seamless way possible such that
 metrics may be added or removed at will and without much friction. To do this, we will use the
-[go-metrics](https://github.com/armon/go-metrics) library.
+[go-metrics](https://github.com/hashicorp/go-metrics) library.
 
 Finally, operators may enable telemetry along with specific configuration options. If enabled, metrics
 will be exposed via `/metrics?format={text|prometheus}` via the API server.

docs/docs/core/09-telemetry.md

@@ -18,7 +18,7 @@ To query active metrics (see retention note above) you have to enable API server
 ## Emitting metrics
 
 If telemetry is enabled via configuration, a single global metrics collector is registered via the
-[go-metrics](https://github.com/armon/go-metrics) library. This allows emitting and collecting
+[go-metrics](https://github.com/hashicorp/go-metrics) library. This allows emitting and collecting
 metrics through simple [API](https://github.com/cosmos/cosmos-sdk/blob/v0.50.0-alpha.0/telemetry/wrapper.go). Example:
 
 ```go