Dynamic linkage for CocoaPods

[ilammy]

Update to latest CLOpenSSL 1.1.10802 which uses dynamic linkage (and removes some architecture slices for that).

Now that CLOpenSSL is using dynamic linkage, we can switch Themis back to using dynamic linkage too (as it was before). The themis pod will have to continue being a dynamic framework Pod to avoid breaking existing builds.

arm64e slice in binary dynamic frameworks causes issues with CocoaPods so it has been removed from CLOpenSSL starting with 1.1.10802. However, Carthage builds use Xcode project which still requires arm64e. Remove arm64e from the architectures list as it is not available now.

Checklist

• Change is covered by automated tests
• Changelog is updated (in case of notable or breaking changes)

[ilammy]

The builds is currently broken, should fixed once #751 is merged (and the build restarted).

[ilammy]

I don't really like to pin OpenSSL versions, but @vixentael is being extra paranoid, and I'm honestly tired of this madness, so whatever floats your boat.

[vixentael]

yeah, sorry, i'm tired of being pushed to update our own libraries urgently because they suddenly introduce breaking changes.

[ilammy]

As it turns out, code examples are broken with Themis 0.13.5 once CLOpenSSL 1.1.10802 has been released. Given that CI is broken, we're currently ignoring it (again, and again).

[ilammy]

As it turned out in #752, the proper way to pin Carthage binary dependency is to use == in Cartfile:

binary "https://example.com/spec.json" == 1.2.3

which will then result in the following Cartfile.resolved

binary "https://example.com/spec.json" "1.2.3"

One cannot use "1.2.3" – tag-like spec – for binary dependencies since they are only versioned (by the JSON spec), they have no associated repository.