Decide what to do about /-/inspect #465
It's not clear to me what this endpoint should do now as a result of #419 - it's still useful to be able to introspect databases for tools like datasette-registry, but since we aren't pre-calculating introspection data any more I need to rethink the approach.
For one thing, this endpoint may need to be paginated. Or maybe it should be split up into separate endpoints for each connected database? Those should probably be paginated too seeing as fivethirtyeight has 400+ tables.
The main use-case for this endpoint now is going to be Datasette Registry (which really needs some more love).
That tool needs to be able to query a Datasette and find out:
Maybe a smarter approach will be the older idea of having a separate inspect for each database (and maybe each table):
Either way, I'm going to decouple this from milestone 0.28.