Feature-Fluid Compute Pricing

**Note**
> * Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
> * Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do * not help prioritize the request
> If you are interested in providing additional feedback, please leave a comment

**Description**
When calling 3rd party services such as LLMs, the lambda sits blocked on the network read, which customers are charged for, while that CPU is very likely doing other useful work. This at least is my understanding, and this doesn't seem right.

Vercel has added a variant of this called 'Fluid Compute Pricing' (on top of Lambda??): https://vercel.com/docs/functions/usage-and-pricing

Lambda should natively support this! And better i'm sure.

**Additional context**
Some of the other issues might be related to this in theory so happy to see this closed if other use cases take on this fundamental shift;

https://github.com/aws/aws-lambda-roadmap/issues/57
https://github.com/aws/aws-lambda-roadmap/issues/16

Empieza revisando los issues enlazados de la hoja de ruta de AWS Lambda y la documentación de Vercel Fluid Compute Pricing. El issue no especifica archivos, pruebas ni un punto de entrada para la implementación; primero establece el modelo de precios previsto, el alcance y la relación con esos issues existentes. La tarea se consideraría terminada cuando exista una dirección de producto e implementación aceptada, no cuando haya un cambio de código autocontenido.

Escrito por el modelo de indexación a partir del texto del issue.