Improve usefulness of error throws

[Nick-Lucas]

For instance:

SQL 'Syntax Error' from the SQL provider:
Bean.FindIterator("Table", "id = {0}", 7)

Should be:
Bean.FindIterator("Table", "WHERE id = {0}", 7)

Behaviour like this isn't always totally clear. We could at least handle syntax errors by throwing a custom LimebeanSyntaxError() exception with the problem SQL query included for analysis. Digging through an assembly's code until you realise you missed a 'WHERE' when you thought the API was doing that isn't super friendly.