feat(ses): implement real SES inbound receipt rule action execution

[vieiralucas]

Summary

• The /_fakecloud/ses/inbound endpoint now actually executes receipt rule actions instead of just evaluating them
• S3 actions: stores the email body as an object in the specified bucket with the configured key prefix
• SNS actions: publishes an SES Received notification to the specified topic, with full fan-out to SQS/Lambda subscribers
• Lambda actions: invokes the specified function with an SES event payload matching the real AWS format

Test plan

• E2E test: S3 action stores object in bucket with correct key and content
• E2E test: SNS action publishes notification that fans out to SQS subscriber
• All 11 existing SES receipt rule tests still pass
• cargo clippy -D warnings clean
• CI green

---

Summary by cubic

Make /_fakecloud/ses/inbound execute SES receipt rule actions for real, enabling cross-service delivery. S3, SNS, and Lambda actions now run and mirror AWS behavior via the DeliveryBus.

• New Features

  • Executes receipt rule actions in /_fakecloud/ses/inbound.
  • S3 actions: store email body in the target bucket with the key prefix and message ID.
  • SNS actions: publish a "Received" SES notification to the topic with fan-out to SQS/Lambda.
  • Lambda actions: invoke the target function with a real SES event payload.
  • Integrated with the existing DeliveryBus for SNS/SQS/Lambda wiring.

• Dependencies

  • Add bytes, md-5, and uuid to fakecloud-server.

^{Written for commit 28e42a0. Summary will update on new commits.}

[cubic-dev-ai]

No issues found across 3 files