Auto categorize CLI flag

[jake-perkins]

This adds a new --autoCategorize flag to the CLI which will categorize the conventional commits to keep a changelog format for the generated changelog

Example output runs

yarn auto-changelog update --autoCategorize

---

Uncategorized

• tweaking configs
• newline
• update changelog
• remove logs
• testing
• reset changelog
• readme
• format changelog

Added

• feat: testing conv commit feat
• feat: categorize conventional commits

Fixed

• fix: format
• fix: testing conv commit

[sethkfman]

LGTM

[mcmire]

This makes sense to me, I just had some suggestions.

It doesn't appear that we have any tests for updateChangelog. However, would you mind adding some in an update-changelog.test.ts file for your new changes? It doesn't have to test any of the existing functionality, just your addition.

[mcmire]

Looks like there are some lint failures to fix, and then I can approve.

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

[jake-perkins]

@mcmire @cryptodev-2s would you mind re-reviewing/approving ?
For the reasons outlined in this https://stackoverflow.com/questions/51269431/jest-mock-inner-function
at the request to add unit tests for the update flow I had to move some of the read interactions to a seperate module to allow the inner mocking to get the desired testing coverage of use-cases. Let me know of any questions/concerns!

[mcmire]

Thanks for taking care of this! LGTM.