major: v3 (plugins and monorepo support)

[tunnckoCore]

Support for #1 monorepos, and #2 plugins.

[codecov]

Codecov Report

Merging #3 into master will increase coverage by 9.09%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master       #3      +/-   ##
==========================================
+ Coverage   63.63%   72.72%   +9.09%     
==========================================
  Files           1        1              
  Lines          11       11              
==========================================
+ Hits            7        8       +1     
+ Misses          4        3       -1

Impacted Files	Coverage Δ
src/index.js	72.72% <0%> (+9.09%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7254d1d...3b58f32. Read the comment docs.

[tunnckoCore]

ref: conventional-commits/conventionalcommits.org#118 (comment)

Do not support mono-repo setups. Lerna is doing great.

[tunnckoCore]

Yet, we may create lerna plugin, so we can use it under the hood, just like the npm one.

[tunnckoCore]

The workflow basically will be

1. If normal repo: activate the Github APP and install the CLI
2. If monorepo: deactivate (or non activating it at all) GitHub APP and use the lerna plugin for the CLI (e.g. standard-release --plugin lerna) which will also create github releases (so requires the GH_TOKEN env in CI). It will also use lerna changed under the hood.

[tunnckoCore]

The npm plugin (default) should also support dist-tag flag.
The lerna plugin should also support the dist-tag. Basically use dargs to pass all coming flags to lerna

[tunnckoCore]

• Make --dry-run alias for the --dry flag.
• Rename --token to --npm-token and --gh-token / --github-token
• Mirror & sync from env the GH_TOKEN (lerna required, for gh releases) and GITHUB_TOKEN