fix: Allow passing boto3 config to all AWS Bedrock classes

[AnesBenmerzoug]

Related PR

• follow-up to fix: avoid bedrock read timeout (add boto3_config param) #1135

Proposed Changes:

• Updated class init signatures to allow passing additional and optional boto3_config dictionary and use it when initializing boto3 client.
• Updated tests accordingly

How did you test it?

• Tested locally by running hatch test

Notes for the reviewer

This is a follow up to PR !1135 that simply applies the same change to all other aws bedrock classes (AmazonBedrockDocumentEmbedder, AmazonBedrockTextEmbedder, AmazonBedrockChatGenerator).

Checklist

• I have read the contributors guidelines and the code of conduct
• I have updated the related issue with new insights and changes
• I added unit tests and updated the docstrings
• I've used one of the conventional commit types for my PR title: fix:, feat:, build:, chore:, ci:, docs:, style:, refactor:, perf:, test:.

[CLAassistant]

All committers have signed the CLA.

[AnesBenmerzoug]

@davidsbatista I could not completely sign the CLA because I accidentaly some of the commits without configuring my email address. Should I leave it like this or is it okay to update the author of those commits and force-push the change?

[davidsbatista]

@davidsbatista I could not completely sign the CLA because I accidentaly some of the commits without configuring my email address. Should I leave it like this or is it okay to update the author of those commits and force-push the change?

You need to sign the CLA in order for the PR to be merged, so it seems you will need to update the author of these commits.

[davidsbatista]

@AnesBenmerzoug thanks for this contribution! I've left some comments regarding backward compatibility. I've also asked my colleague @vblagoje to do a second review.

[davidsbatista]

@AnesBenmerzoug remove the parameterization of all the tests, and instead do a test such that:

• Create and serialize a new instance without boto3config, then load/deserialize that object, and assert that new deserialized object is exactly the same as the initially created instance

[AnesBenmerzoug]

@davidsbatista Sorry for the delay. I am not quite sure I understand your suggestion. I believe the tests with the parametrization already test the serialization and deserialization of the different bedrock instances with and without the boto3 config. Could you please explain what you meant more clearly?

[davidsbatista]

sorry, this was a misunderstanding from my side - I think we could remove that parameterization but it doesn't hurt to be there.

I've approved your PR - you just need to sign the CLA

[davidsbatista]

LGTM

[AnesBenmerzoug]

@davidsbatista Thanks! I have already signed the CLA.
For some reason after I merged main into my branch, a commit made by the @HaystackBot found its way into my branch and it's the one account that didn't sign the CLA.
Is there a way to fix this?