Handle docker container creation error

[hawflau]

Which issue(s) does this change fix?

#6510

Why is this change necessary?

To catch and handle docker container creation errors when running sam local invoke, sam local start-api and sam local start-lambda

How does it address the issue?

Catch the error and propagate it to CLI

What side effects does this change have?

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.

[mndeveci]

Changes LGTM! Can we add any integration tests that we can validate the changes?

[jysheng123]

I think the code looks fine, but im not too sure if this would fix the customer's issue specifically. I think the customer is asking for validation before trying to create the container that will say the memory size is invalid, the code changes here looks like it will just do validation during the invoke, but it should be validating during the SAM CLI build step.

[hawflau]

To summarize before merging

The change in this PR is to catch and handle Docker Container Creation Error and show a message about the error and telling customer to check the template. SAM CLI provides the sam validate --lint command to catch template issues.

The expectation on the issue #6510 was "Validation errors would be shown when the SAM config is loaded, before the values are used for building and builds would not succeed when invalid values are used", which was captured in #3244 as a feature request.