[Lambda] [request]: Create k8s proxy/ingress controller to test containers designed for lambda locally.

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) 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 working on this issue or have submitted a pull request, please leave a comment

**Tell us about your request**
What do you want us to build?

It would be great if we could have some kind of a facility on Kubernetes locally (minikube, k3s etc) which emulates a HTTP lambda container runtime so developers can test their microservices locally on kubernetes without access to the AWS cloud.

As documented in https://aws.amazon.com/blogs/aws/new-for-aws-lambda-container-image-support/ containers can be tested using a command like this using the `aws-lambda-runtime-interface-emulator`

`curl -XPOST "http://localhost:9000/2015-03-31/functions/function/invocations" -d '{}'`

However it would be better if it could be wired into an ingress controller so it could be invoked like it would be on an api gateway, therefore cross-microservice integrations could be tested easily.

**Which service(s) is this request for?**
None of the above.. a developer facility only.

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
What outcome are you trying to achieve, ultimately, and why is it hard/impossible to do right now? What is the impact of not having this problem solved? The more details you can provide, the better we'll be able to understand and solve the problem.

Can't run lambda docker containers integrating with each other easily.
**Are you currently working around this issue?**
How are you currently solving this problem?

No current work around..

**Additional context**
Anything else we should know?

**Attachments**
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)

Start with the AWS Lambda container image support documentation and the aws-lambda-runtime-interface-emulator invocation endpoint shown in the issue. Compare the proposed local Kubernetes setup on minikube or k3s with ingress-controller behavior and determine how cross-container requests should be routed. Done means Lambda containers can be invoked locally through an ingress-like interface without AWS access.

Written by the indexing model from the issue text.