feat: Add support for Bedrock Guardrails streamProcessingMode

[mattref]

Description

By default, when using Bedrock Guardrails alongside ConverseStream requests, the guardrails operate in "Synchronous mode", which may or may not be desired.

This PR adds a new attribute, guardrail_stream_processing_mode, to BedrockConverse, allowing users to configure the streaming response behavior when using guardrails in a streaming fashion.

Supporting Documentation:

• https://docs.aws.amazon.com/bedrock/latest/APIReference/API_runtime_ConverseStream.html#bedrock-runtime_ConverseStream-request-guardrailConfig
• https://docs.aws.amazon.com/bedrock/latest/userguide/guardrails-streaming.html

Related:

• Amazon bedrock guardrails #17281

Version Bump?

Did I bump the version in the pyproject.toml file of the package I am updating? (Except for the llama-index-core package)

• Yes
• No

Type of Change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Your pull-request will likely not be merged unless it is covered by some form of impactful unit testing.

• I added new unit tests to cover this change
• I believe this change is already covered by existing unit tests

Suggested Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added Google Colab support for the newly added notebooks.
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I ran uv run make format; uv run make lint to appease the lint gods

[mattref]

I didn't feel that there was a need to add guardrail_stream_processing_mode here, as it's not pulled from kwargs.

To be fair, I'm also not too sure why guardrail_identifier and guardrail_version were put here either

[mattref]

Not too sure about the failed prettier linting 😅

[AstraBert]

lgtm

[AstraBert]

For linting, I advise running:

uv pip install pre-commit
pre-commit install
pre-commit run -a
git add .
git commit -m "ci: lint" # linting is now applied at commit time by pre-commit hooks
git push <your-origin> <your-branch>

[mattref]

@AstraBert Thanks for the review! I just rebased the branch & bumped the version to 0.10.7 instead of the original 0.10.6.

Regarding the linting, it looked good on my end hence why I was confused about the "prettier" failure 😅

edit: Looks like it's passing now anyways 🤷‍♂️

[AstraBert]

Yeah, most of the times you just need to update your branch to make these "unexplainable" linting problems go away :)