Add support for precompiled statements

1. I think it will be helpful to have in LowLevel getter for underlying sqLiteOpenHelper. The same thing has been already implemented in StorIOContentResolver.LowLevel and it can solve problems with such particular thinks like precompiled statements if user will need it.
2. To complete support for prepared statements I suggest to add methods to StorIOSqlite like compiledExecute, compiledUpdateDelete, compiledInsert that will take a special type of resolver to bind arguments. @artem-zinnatullin @karlicoss @thevery any thought? Refs #427

[artem-zinnatullin]

Hm. I was thinking about different implementation: on the Query + StorIOSQLite level.

Since our Queries are immutable, we can actually create precompiled statement per query (and as ThreadLocals if needed) and store them as as fixed size LIFO map in SQLiteOpenHelper so if we have precompiled statement for Query — use it, otherwise — precompile and use it!

I don’t want to add any new public API for this feature if possible.

Does it sound ok? Please cc Stas, also known as “Stas — DB EXPERT”, here

[artem-zinnatullin]

add this feature to v1.12.0 as an experimental one (similar approach as new features are introduces to RxJava library), which could be enabled by users who looks for performance boost and it could be turned on by default for later versions. What do you think?

SGTM, @nikitin-da you’ll be able to test it in Yandex.Mail since it uses DB all the time and see if it increases performance or not!