feat: add new lambda feature

[Fishrock123]

For interacting with lambda_http, part of the official awslabs toolkit.

Needs more real testing. TBD.

This is easier to do in Tide directly because otherwise you have to make a wrapper, which seems unnecessary (though I could be convinced that perhaps this is still better in a separate crate).

[adam-the]

This looks good and works fine for me after testing a few use cases. Only gripe I had was that binary is returned for all content types, but I couldn't find a better solution than just switching out the relevant code for lambda_http::Body::Text(body.into_string().await?).

Maybe we could pass the expected body type as a generic or something? I don't like the idea of checking the headers to find out what type should be returned.

This is easier to do in Tide directly because otherwise you have to make a wrapper, which seems unnecessary (though I could be convinced that perhaps this is still better in a separate crate).

I think it's a good idea to support it here and probably not in a separate crate, cause AWS is one of extremely few services that work like this, plus as you say, you'd then have to write a wrapper as well.

lambda-http 0.4.0 uses explicit lifetimes: 7211131

[Fishrock123]

I ended up doing this as the "lambda-http" for the Tide-wrapping framework I maintain for my employer: https://github.com/eaze/preroll#list-of-optional-add-on-features

[adam-the]

I've just had a quick look over tide-lambda-listener; by comparison to this solution, it seems unnecessarily complicated? I don't see any practical difference functionality wise - how come you chose that solution over this?

[Fishrock123]

Oh right. This is also available standalone as https://github.com/Fishrock123/tide-lambda-listener, which I completely forgot about.