Db-to-sqlite

- Upgraded for compatibility with SQLAlchemy 2.0. [46](https://github.com/simonw/db-to-sqlite/issues/46)
- Now documented to work with MS SQL Server. Thanks, Ryan Cheley. [37](https://github.com/simonw/db-to-sqlite/pull/37)

- New `--postgres-schema` option for specifying a different PostgreSQL schema, thanks Jeremy Dormitzer. [29](https://github.com/simonw/db-to-sqlite/pull/29)
- Correctly handles table names that need escaping, such as `user` in PostgreSQL. [25](https://github.com/simonw/db-to-sqlite/issues/25)
- Empty tables are now created in the SQLite database with a matching schema, rather than being skipped. [28](https://github.com/simonw/db-to-sqlite/issues/28)
- Connection strings starting with `postgres://` are treated as if they started with `postgresql://`. [34](https://github.com/simonw/db-to-sqlite/issues/34)

- Added support for compound primary keys. 26

- Changelog badge and project_urls for the [PyPI listing](https://pypi.org/project/db-to-sqlite/).

Bumped to `sqlite-utils` 2.9.1. This fixes two things:

- Decimal columns are now supported. They become FLOAT columns in SQLite.
- Fixed a bug where columns that were a combination of integers and nulls were incorrectly stored as TEXT, not INTEGER.

I made a mistake with the release of 1.1 to PyPI - this fixes it.