chore: rename module to @prometheus/client_js

[cjihrig]

This commit updates the project name from prom-client to @prometheus/client_js to reflect the recent move.

This is my first time contributing to this project under any package name, so please let me know if anything here is incorrect.

[slagiewka]

I know that @krajorama mentioned client_js as the desired state in #750 (comment). But this might've been intended to point to the repository name, not package name.

Reality check:
Python: pip install prometheus-client
Ruby: gem install prometheus-client
Rust: cargo add prometheus-client

Go is of course an outlier since it imports directly from domain's namespace. And in Go packages with _ in name are more commonplace.

prometheus-client is taken on npm. @prometheus/client would be more aligned with the npm ecosystem.

[krajorama]

I don't have a strong opinion, I feel that @prometheus-io/client_js would be nice to reflect the name of the repo it comes from, but I'm ok with @prometheus-io/client as well. (Note : currently Prometheus publishes packages under prometheus-io).

@jdmarshall any preference?

UPDATE: as far as I see I can freely add @prometheus organization, so we can do @prometheus prefix as well.

[cjihrig]

Personally, I think @prometheus/client would be the nicest and clearest, since that is what people will be typing when they install. However, if @prometheus-io is already being used, then I think @prometheus-io/client would be the best option to avoid confusion and managing multiple package scopes. The _js probably isn't needed since the package is coming from npm.

[jdmarshall]

These are going to conflict with another PR that simplifies the names for the benchmarks. I'm landing that momentarily.