Transparent decryption with metadata replacing

[Lagovas]

• Added processing DataRowDescription and ParameterDescriptionData. In DataRowDescription now we replace OID values that tell drivers which data types will be returned. In ParameterDescriptionData we replace OIDs for parameters in prepared statements. To tell apps that they should pass string value instead of binary (that will be changed on Acra side)
• Extend encryptor config with two new fields: default_data_value and data_type. Last values generated via protobuf in similar way as token type.
• Added support of text format values in binary protocols (prepared statements). Previously was supported only binary formatted values.
• Refactored QueryDataEncryptor to re-use functions related to parsing placeholders and saving encryptor's settings in context/client session values
• Extended ClientSession interface to provide KV interface and store session related data for client/db packet handlers
• Removed legacy acra-log-verifier config file from configs folder
• Added updating context (ctx) with flag after successful decryption (base.[MarkDecryptedContext|IsDecryptedFromContext]). Needs for replacing with default values binary data types that hard to determine when they was untouched
• Removed legacy interface method SubscribeOnColumnDecryption and all related methods of proxies due to not using
• Refactored PgSQLDataEncoderProcessor. Now it used not only for tokenization, but for decoding all input data from database and encoding before sending to client. Also removed this logic from PostgresqlDecryptor which now responsible only for database packet parsing. All other data manipulations moved to OnQuery/OnBind/OnColumn subscribers
• Additionally removed DecodedData wrapper for Column structs used by decryptor

It's ready to review. Probably last changes will be related to encryptor's config validation and updating changelogs (after that I will change it from status Draft). So welcome to review.

Checklist

• [+] Change is covered by automated tests
• [+] The coding guidelines are followed
• [+] Public API has proper documentation in the Acra documentation site or has PR on documentation repository with new changes
• [-] CHANGELOG.md is updated (in case of notable or breaking changes)
• [-] CHANGELOG_DEV.md is updated
• [ ] Benchmark results are attached (if applicable)
• are up-to-date (in case of API changes)

[G1gg1L3s]

you prefer that I will fix current comments, commit, wait approval and after that split it into the separate PRs and review one more time or we can finish it as is and keep it in mind in the future?)

I think we can left this PR as is :)