Over-stringent SQLite validation

[fvankrieken]

Expected behavior and actual behavior.

As part of resolution to #8430, validation was added to ensure that sql commands being used are valid for sqlite (and prompt user to use OGR SQL dialect rather than SQLite in cases where appropriate). However, these cases check that sql statements start with "{command} ", the final character there being a space. However, other whitespace characters are not considered valid, even though "SELECT\n" is a valid beginning to a SQLite select clause. This issue arose for us because of sql queries defined in yml files that get fed into a gdal.VectorTranslate call in python, and it's helpful to format the queries with newlines.

Steps to reproduce the problem.

Perform any call to ogr2ogr with sqlite dialect and sql statement starting with "SELECT\n". If more details/example data are needed, happy to provide, but from the code hope that this issue is self-evident.

Operating system

Debian bookworm

GDAL version and provenance

I was using a built-from-source install of 3.8.3