fix: Explicitly exit when container is out-of-memory

[mildaniel]

Which issue(s) does this change fix?

#6260

Why is this change necessary?

When an invoke container exits because it's out of memory, SAM CLI doesn't communicate this to customers and it's unclear why the invocation failed.

How does it address the issue?

Explicitly note the exit reason is out-of-memory and exit with return code 1 instead of 0.

What side effects does this change have?

Existing invocations that fail due to out-of-memory will return exit code 1.

Mandatory Checklist

PRs will only be reviewed after checklist is complete

• 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.

[mildaniel]

This check is admittedly a little weird, but mypy won't like it if we don't do this, and the reason we return a bool here is to follow the legacy pattern in container_manager.