Use PyPi dependency for durable functions integration tests

[bchampp]

Which issue(s) does this change fix?

Why is this change necessary?

We recently reverted a change to use the PyPi dependency directly when running the durable functions integration tests. The original change was failing because a bug was introduced in the latest version of the SDK, specifically in how we deserialize the invocation payload.

The integration tests (and users, depending on which SDK version they were using) would have seen failures like this:

Error:  ExecutionError: Unexpected payload provided to start the durable execution. Check your resource configurations to confirm the durability is set.
Traceback (most recent call last):
  File "/var/task/aws_durable_execution_sdk_python/execution.py", line 269, in wrapper
    raise ExecutionError(msg) from e

How does it address the issue?

This PR adds the latest emulator binaries for durable functions, namely including these two changes:

1. refactor: use to/from_json_dict for operation serdes aws-durable-execution-sdk-python-testing#185,
2. fix: convert InvocationCompletedDetails to unix milliseconds aws-durable-execution-sdk-python-testing#194

What side effects does this change have?

None - integration tests (using the latest SDK) are passing 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.