Feature: Runtime Execution Simulator

Name Pending.

Testing Lambda code can be difficult / unwieldy. While SAM exists for all supported languages, it is pretty limited in ergonomics, difficult to integrate with in CI, makes testing / infrastructure management unnecessarily complicated, and still requires further orchestration.

In an ideal world, we'd be able to "just" create a runtime with the corresponding service, add all the hooks, tracking, and tracing that we need, execute requests on top, and then verify the results, benchmark, get flamegraphs, etc, all without actually ever deploying, and all from a single `tokio::test`.

I have added a basic server in #1086, so this backlog issue is for extension / reuse of the implementation.

We should start from an internal implementation, and eventually publish a crate so that users can depend on it and integrate it in their CI.

Utilisez le serveur de base ajouté dans l’issue #1086 comme point d’entrée, puis examinez comment il pourrait être étendu ou réutilisé pour l’exécution du runtime local. Avant d’implémenter quoi que ce soit, clarifiez le premier jalon interne et les critères d’acceptation, car l’issue couvre actuellement les hooks, le tracing, l’exécution des requests, le benchmarking et la publication ultérieure du crate.

Rédigé par le modèle d'indexation à partir du texte de l'issue.