Use ash_sqlite for mssql and Ecto.Adapter.Tds

[user20230119]

"Merge" ash_postgres and ash_sqlite

There will always need to be two separate data layers, because Ash data layers are not pure SQL drivers. They make choices based on what a given data source’s capabilities are, that kind of thing. For example, AshPostgres supports aggregates via inner lateral joins, but AshSqlite does not support that, and if we want to support aggregates with it we will need to figure out a different strategy later. Same is with atomics, because sqlite doesn’t have a way to raise an error (that I could find) in…

After reading this post, I don’t know if we should start with AshPostgres or AshSqlite as a base for MSSQL.