Use microprofile reactive-messaging for SQS and add pattern resilience for messaging

[matheusandre1]

This pull request covers, Closes #46 , Closes: #45

SQS.java persisted a Record in PostgreSQL (QuarkusTransaction.requiringNew)
Then, it sent the result to SQS via @Outgoing("whatsapp-recognized")

Instead of sending directly to SQS, we write the output message to an outbox table within the same transaction that persists the Record. A separate process (relay) reads from this table and sends it to SQS asynchronously and resiliently.

I believe that so far it follows good practices of the outbox pattern.

Guaranteeing:

• Atomicity: Record and OutboxMessage are in the same JPA transaction
  -Resilience: If the relay fails to send to SQS, the message remains PENDING and is retried
• Ordering: Messages are processed in createdAt order; FIFO of the destination queue is preserved via messageGroupId
• Idempotence: The destination queue has content_based_deduplication = true in Terraform
• Non-blocking: The relay does not participate in the transaction consuming the original message

[mcruzdev]

Great work!

[mcruzdev]

Possible Closes #46 , , but this will affect the other pull request I made, the #200, It's very likely that there will be some conflict, what would be the best practice for this cc: @mcruzdev ?

Let's merge this one first and after you need to change the another haha, there is no way to escape!

[matheusandre1]

Take a look @mcruzdev the outbox pattern requires idempotence, right?