ci: publish workflow

[Shinigami92]

This is a GitHub action workflow that let's maintainers of Faker run a npm publish process, so that the package @faker-js/faker will be published to npm registry.

It requires that one of the maintainers create a new access token on NPM for the @faker-js/faker package, or for the @faker/* orga-scope.
This then needs to be configured in GitHub as a secret with the name NPM_TOKEN, so it can be picked up by the CI.

Note that publish will run the prepublishOnly script that is configured in the package.json

This workflow will NOT "craft" a release, nor will it create tags/releases on github.
It just and only automates the publishing to npm.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.57%. Comparing base (9348138) to head (8ed6b41).

Additional details and impacted files

@@            Coverage Diff             @@
##             next    #2591      +/-   ##
==========================================
- Coverage   99.57%   99.57%   -0.01%     
==========================================
  Files        2846     2846              
  Lines      248715   248715              
  Branches      655     1015     +360     
==========================================
- Hits       247669   247668       -1     
- Misses       1017     1018       +1     
  Partials       29       29              

see 2 files with indirect coverage changes