Add SQL text to exceptions

I'm experiencing an issue that appears to be related to #565, but because the error is a syntax error, there's no opportunity for me to examine the actual text that got sent to the database. It doesn't get logged in Oracle's metadata tables (like V$SQL), and unfortunately, OracleException doesn't seem to contain the SQL text, either. Maybe I could get it via some profiling tool, but this feels like overkill and and isn't applicable if you're not using a web application.

It would be nice if I could see the exact SQL text when errors occur so I don't have to guess as much about what the problem might be. I believe a simple way this could be added is by storing it the Data property of an exception:

try {
    // Do whatever Dapper does
}
catch (Exception ex) {
    ex.Data["fullSql"] = actualSqlSentToTheDb;
    throw;
}

Start by tracing Dapper's database execution and exception paths to identify where the submitted SQL is still available. Confirm the desired behavior with a syntax-error scenario and verify that the resulting exception exposes the exact SQL text through its Data property.