Update of underlying sqlite3mc library version

[utelle]

Today I released SQLite3 Multiple Ciphers 1.8.0. This version adds a new cipher scheme, Ascon 128 (and fixes a few issues that are not relevant in the context of SQLitePCL.raw).

I'd like to ask which procedure I should follow to update sqlite3mc / e_sqlite3mc in your cb repo. The new version compiles without problems in my fork. Additionally I'd like to ask whether issue ericsink/cb#20 should be included in the process.

[ericsink]

I'll try next week to take a look at this, and the cb issue you mentioned.

I'm also trying to get the Xamarin support removed, and I'd like to keep that separate from other changes. In other words, I was thinking I might do 2.2.0 which is exactly the same as 2.1.7 except with Xamarin support removed.

So I need to decide whether this issue would be 2.1.8 or 2.2.1.

[utelle]

So I need to decide whether this issue would be 2.1.8 or 2.2.1.

I'm fine with you postponing this issue until 2.2.1.

My concern is simply to define a procedure for future updates that is convenient for both of us.