pindexer: name the database in error messages

[conorsch]

Someone running pindexer for the first time reported a first-run error, which read:

Error: error returned from database: relation "block_details" does not exist

Any pindexer instance requires two (2) databases: read-only access to the raw CometBFT ABCI events db, and full write access (with schema creation privileges) to its own database, to store the munged events. The table block_details only exists in the latter, so that's what the error message is pointing to, but a user likely won't know that ahead of time. Let's wrap the error message with more context to guide the user.

Given how frequently we're updating the pindexer schema, recommending resetting that db from scratch is maybe a good idea too.

[cronokirby]

An idea here is that we can maybe add some things to the app view trait to give each component a name and monotonic version, so that we can store metadata about which views the database was compiled with, and then error if the set has changed, and the database is not empty.

This would allow us to give a detailed error explaining what needs to be done.