[FEATURE] Serialize conversation message processing

[NagithaAbeywickrema]

Feature Description

Implement sequential message processing for user conversations to prevent concurrent handling of multiple messages from the same conversation

Problem Statement

AK currently does not wait until a message is processed to start processing another message. This becomes an issue specifically when processing social media message webhooks, where if a user sends another message before the previous one is processed, the system might process both in parallel. This affects the sequential nature of the conversation

Proposed Solution

Use AWS SQS with a topic/ queue per conversation

Use Case

Everyone who values sequential processing of a conversation would benefit from this (Specially social media messaging)