Publish as cz instead of commitizen on NPM

[felipecrs]

It would be awesome if we could keep consistency between the CLI name cz and the NPM package name, commitizen.

This would allow people to:

1. Use npx cz everywhere, even when not installed. Refs https://github.com/commitizen/cz-cli/issues/762#issuecomment-692109333.
2. Set up their repositories easily with npm i -D cz.
3. Get rid of the confusion caused by npx git-cz, which uses @streamich's git-cz instead of commitizen's official, by advertising npx cz more instead of npx git-cz.

For this to happen we would need:

1. Maintainers approval
2. @OmgImAlexis approval, because she owns the cz namespace on NPM. What do you think, @OmgImAlexis?

[OmgImAlexis]

I’d be okay giving it up granted it goes to the org account and not a single person.

[petermetz]

Maybe this is off-topic, maybe not. Been using commitizen and what I believe to be the original git-cz package (assumption) together in the same repo and been getting a strange, flaky issue because of it. I realized that it's because both packages declare git-cz as a binary and probably collide in an nondeterministic manner due to how npm does package installs in parallel (guess). So, is this a bug? Is commitizen "squatting" on the git-cz binary if we assume that packages should declare binaries matching their name only, to avoid conflicts like this? Or do I have the chicken egg equation backwards and commitizen is the OG implementation?

[OmgImAlexis]

Hate to be that person but with the recent activity to this repo maybe it's time to bump it.