[BUG] Published API causes unhandle exceptions for larger message map

## 🚨 **Please Note** 🚨

To ensure efficient investigation of the issue, please fill out the fields below with as much detail as possible. **Reports that do not follow this template may be closed without notification.** We appreciate your cooperation.

## 🐞Describe the bug

When using the published API and the message map is too large, it will cause the sqs consumer lambda (*SqsConsumeHandler*) unhandled exception and terminate.

See the screenshot below.

## 🔄 To Reproduce

Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

## 📷 Screenshots

If applicable, add screenshots to help explain your problem.

## 🔎 Logs for Chat Issues

If the issue occurs during a chat interaction, please check the following logs on Amazon Cloudwatch Logs and include the relevant entries in your issue:

- `/aws/lambda/BedrockChatStack-BackendApiHandlerXXXX`
- `/aws/lambda/BedrockChatStack-WebSocketHandlerXXXX`

## 🔎 Logs for Bot Creation/Update Issues

If the issue occurs during bot creation or updating, please check the execution records of the AWS Step Functions state machine named `EmbeddingStateMachineXXX` and include the details in your issue.

## 📝 Additional context

Add any other context about the problem here.

Start at the published API path and the named SqsConsumeHandler entry point, then reproduce the failure with a larger message map and inspect the relevant AWS CloudWatch logs. Done means the SQS consumer no longer terminates with an unhandled exception for oversized message maps.

Written by the indexing model from the issue text.