Provide more informative error messages if the input for SqlImplementation is not a valid sqlite file

[cmungall]

currently if we pass in something invalid to SqlImplementation, it will not complain until after an operation is performed, rather than at connection/instantiation time

furthermore, the stack trace from sql aclhemy can be confusing - see #212

we should fail early with bad SqlImplementation connections (and with implementations in general)