Replace lerna-changelog with changesets

[ijlee2]

Description

I updated @codemod-utils/cli so that, by default, codemod projects use changesets to update CHANGELOG.md and publish the package. pnpm recommends changesets and we might see more frequent releases (in comparison, lerna-changelog hasn't had a release since October 2021).

Why @changesets/get-github-info?

The built-in implementations (@changesets/changelog-git and @changesets/changelog-github) currently pose a large technical risk (the code is complex and in need of refactoring) and generate CHANGELOG's that I don't find useful.

With @changesets/changelog-git

## 0.1.2

### Patch Changes

- f8f2bef: Third attempt at publishing packages

With @changesets/changelog-github

## 0.1.2

### Patch Changes

- [#13](https://github.com/ijlee2/my-project/pull/13) [`f8f2bef`](https://github.com/ijlee2/my-project/commit/f8f2bef08dc907458b0d9e9acabe6301ae0559d0) Thanks [@ijlee2](https://github.com/ijlee2)! - Third attempt at publishing packages

With a custom formatter, we can create CHANGELOG's that help maintainers and end-developers (users) more. The output is inspired from lerna-changelog and will look like:

## 0.1.2

### Patch Changes

- [#13](https://github.com/ijlee2/my-project/pull/13) Third attempt at publishing packages ([@ijlee2](https://github.com/ijlee2))

[ijlee2]

For public repos, one can use the default scopes (none selected). For private repos, however, they will need repo and read:user scopes.

To simplify the instructions, we'll ask maintainers to select the repo and read:user scopes.

[ijlee2]

I added pnpm build to ensure that the latest TS files are compiled, then published.