encrypt/decrypt/stream API docs are missing new commitment_policy parameter

[mattsb42-aws]

I was talking with @seebees about this and noticed that the changes to the encrypt/decrypt/stream API parameters was not documented in the docstrings (and thus the rendered API docs).

[farleyb-amazon]

Thanks @mattsb42-aws . To elaborate, we actually don't intend for callers to directly pass commitment_policy to the encrypt/decrypt/stream APIs; instead, they should be configuring the EncryptionSDKClient with the appropriate commitment policy. We wanted to minimize the number of different places you could configure this option in order to reduce confusion.

However, this does raise another issue, which is that callers currently can pass a commitment policy to these APIs without receiving an error, but the commitment policy will be overridden by the policy in the client. This could definitely be confusing. So I think the fix we should make here is to prevent callers from passing this parameter to the APIs.

[mattsb42-aws]

So I think the fix we should make here is to prevent callers from passing this parameter to the APIs.

++