Update Crypto Verbiage To Clarify We Don't "include" or "implement"

Some of these may need help from dev, others from docs, but it's a docs driven request, so I'm adding . In a few places (mostly around FLE from what I can see), we seem to state that we "include" or "implement" cryptographic algorithms. However, we only wrap capabilities that are available on each platform, as a default implementation of a pluggable interface that the make use of for convenience. So we should refactor any such mentions to clarify.

Here are a few examples (but we should search for more):

• https://docs.couchbase.com/python-sdk/current/howtos/encrypting-using-sdk.html
  • "This library includes cryptographic algorithms you can use out of the box ..."
• https://github.com/couchbase/java-couchbase-encryption/blob/master/src/main/java/com/couchbase/client/encryption/internal/AeadAes256CbcHmacSha512Cipher.java
  • "Implements the AEAD_AES_256_CBC_HMAC_SHA512 encryption algorithm specified by ..."