Sqlite-migrate

- Fixed bug where two different migration sets could not have migrations with the same name. [11](https://github.com/simonw/sqlite-migrate/issues/11)
- This included updating the primary key on `_sqlite_migrations` from `name` to `(migration_set, name)`.
- No longer shows a deprecation warning about `datatime.utcnow()` in Python 3.12. Thanks, [Ed Summers](https://github.com/edsu). [#10](https://github.com/simonw/sqlite-migrate/issues/10)

- New `--stop-after NAME` and `.apply(stop_after=name)` mechanism for applying all migrations up to a specific point. [9](https://github.com/simonw/sqlite-migrate/issues/9)

- Now accepts zero or more paths to migrations files or directories containing migrations files. [2](https://github.com/simonw/sqlite-migrate/issues/2)
- New `-v/--verbose` option, which shows the schema before and after the migrations were applied along with a diff.
- `sqlite-utils migrate data.db --list` now shows a list of previously applied migrations and a list of pending migrations. [5](https://github.com/simonw/sqlite-migrate/issues/5)

- Initial alpha release. [1](https://github.com/simonw/sqlite-migrate/issues/1)