Add the ability to specify Conventional Changelog Options

Description

conventional-changelog-cli has the ability to pass in a json file with various configuration options that are passed to conventional-changelog-core. This would be a convenient option for issue trackers and git repositories that don’t follow the same standards as GitHub.

Here’s an example configuration:

{
  "changelogOpts": {
    "preset": "angular"
  },
  "parserOpts": {
    "issuePrefixes": ["custom-issue-prefix-"]
  },
  "writerOpts": {
    "headerPartial": "{{version}} {{~#if date}} ({{date}})\n  {{~/if}}",
    "commitPartial": "* {{this.subject}} \n\n{{~!-- commit link --}} {{#if @root.linkReferences~}} \n  ([{{hash}}]({{~@root.repoUrl}}/{{~@root.commit}}/{{hash}})){{~else}}{{~hash}}{{~/if}}"
  }
}

[bcoe]

@smeijer @nick-woodward @Tapppi dusting off an old issue as I go through my giant GitHub issue backlog; I don’t hate the idea of introducing a .svrc and standard-version stanza in the package.json to standard-version for controlling a few select configuration options.

I think we should make things a bit less À la cart than conventional-changelog-cli; which suffers from the paradox of choice. yargs has great built in support for this functionality.

If an issue doesn’t already exist, perhaps we could open one to bike-shed some initial configuration options; mainly I think introducing options that would allow us to support platforms other than GitHub, e.g., BitBucket, would be beneficial.

[smeijer]

+1, I would like an option to not include any links. This to make it easy to generate public changelogs for a private repo.