chore: bind lambda RIE to 0.0.0.0 for durable functions

[bchampp]

Which issue(s) does this change fix?

Why is this change necessary?

The Lambda RIE container gets bound to 127.0.0.1 (localhost) by default. The durable executions emulator needs to interact with the RIE endpoint directly - so we're making HTTP calls from within the emulator container across to the RIE endpoint.

In some environments, this isn't accessible by default, and we see errors like Could not connect to endpoint: host.docker.internal... We need to bind the RIE container to 0.0.0.0 instead so it's accessible on any interface. Users can work around this by using --container-host-interface 0.0.0.0, but this should by default.

How does it address the issue?

Updating the DurableLambdaContainer class to override the lambda container container_host_interface parameter to 0.0.0.0.

What side effects does this change have?

Lambda container is always bound to 0.0.0.0 for durable executions.

Mandatory Checklist

PRs will only be reviewed after checklist is complete

• Review the generative AI contribution guidelines
• Add input/output type hints to new functions/methods
• Write design document if needed (Do I need to write a design document?)
• Write/update unit tests
• Write/update integration tests
• Write/update functional tests if needed
• make pr passes
• make update-reproducible-reqs if dependencies were changed
• Write documentation

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.