fix: handle StopDurableExecution payload deserialization correctly

[bchampp]

Which issue(s) does this change fix?

Why is this change necessary?

A customer reported a bug in the SAM CLI with using the StopDurableExecution API over HTTP when passing in the Error object.

How does it address the issue?

There is a bug where the arguments passed from the HTTP client to the lambda client aren't aligned - specifically the stop_durable_execution method needs all expanded arguments for the API, instead of a single argument.

What side effects does this change have?

N/A - works as expected now.

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.