Spectacles should reduce queries run when the errors are duplicated

[DylanBaker]

There are scenarios, such as when a whole table doesn't exist, that every (or almost every) dimension in a view will produce effectively the same SQL error (which is that the table doesn't exist). We run all the queries even though each one doesn't provide additional context and each query takes up time. Ideally, we could spot when these situations are occurring and reduce the number of queries we run.

I don't currently have a suggestion for how to do this. We would need to (a) map error messages for the most commonly used databases and (b) likely internalise the concept of a LookML 'view' in the Spectacles codebase.