feat: add support for 1.17 back

[marco6]

No description provided.

[letFunny]

@marco6 I see that TestIntegration_ExecBindError is failing for some versions.

[marco6]

I see that TestIntegration_ExecBindError is failing for some versions.

@letFunny it is failing for all 1.18.x versions and will keep doing that as the EXEC_SQL command is broken by design. If you remember, we had 2 choices (which the current test clearly is not highlighting):

• support binding only on the first statement (which was the case for 1.17) so db.Exec("INSERT INTO a VALUES (?); INSERT INTO b VALUES (?)", 1, 2) fails (and it is clearly not tested as it wouldn't have looked great!) but on the other side db.Exec("INSERT INTO a VALUES (?)", 1, 2) is checked correctly and fails
• supporting binding on multiple statements (which is the case for 1.18) so the exact reverse. It would be a bit weird to return "error".

There is a "fix" that uses a prepared statement in #383.

[just-now]

Looks good.

[letFunny]

@marco6 so you are fixing the tests as part of another PR, then it's okay for me. I just don't want tests always failing.

[letFunny]

Just one question and LGTM!