Allow DF Activity Functions to have multiple output bindings

[davidmrdavid]

Issue describing the changes in this PR

resolves #646
replaces #700

Pull request checklist

• My changes do not require documentation changes
  • Otherwise: Documentation issue linked to PR
• My changes should not be added to the release notes for the next release
  • Otherwise: I've added my notes to release_notes.md
• My changes do not need to be backported to a previous version
  • Otherwise: Backport tracked by issue/PR Allow DF Activity Functions to have multiple output bindings (v4.x/ps7.0) #703, Allow DF Activity Functions to have multiple output bindings (v3.x/ps7) #704
• I have added all required tests (Unit tests, E2E tests)

Additional information

Previously, the Function BindOutputFromResult would only bind output values for non-DF Function types. It appears this was put in place to prevent DF orchestrators from having multiple output bindings. However, the implementation also prevented Activity Functions from having multiple output bindings, which led to the bug report linked above.

This PR refines the logic to apply only to orchestrators.

[davidmrdavid]

I'm unsure if I need to mark the checkbox to backport this PR, please let me know!

[michaelpeng36]

I think this PR would be a good candidate for backporting due to the generic nature of the issue. However, for now, I think we should restrict this change to the v3.x/ps7, v4.x/ps7.0, and v4.x/ps7.2 branches since other branches do not have the same TODO comment.

[davidmrdavid]

Thanks @michaelpeng36! I'd appreciate a review as well to move this along :)

@AnatoliB: do you agree with Michael's backporting versions suggestion? I want to make sure we target the version of the affected customer

[michaelpeng36]

LGTM

[Francisco-Gamino]

Thanks @michaelpeng36! I'd appreciate a review as well to move this along :)

@AnatoliB: do you agree with Michael's backporting versions suggestion? I want to make sure we target the version of the affected customer

Thanks @davidmrdavid -- We should port this fix to v3.x/ps7 and v4.x/ps7.0 only (as a cherry picks). When we do new releases for v4.x/ps7.2, we will merge the dev branch into v4.x/ps7.2. Let me know if you have any other questions. Gracias!

[AnatoliB]

Thanks @michaelpeng36! I'd appreciate a review as well to move this along :)
@AnatoliB: do you agree with Michael's backporting versions suggestion? I want to make sure we target the version of the affected customer

Thanks @davidmrdavid -- We should port this fix to v3.x/ps7 and v4.x/ps7.0 only (as a cherry picks). When we do new releases for v4.x/ps7.2, we will merge the dev branch into v4.x/ps7.2. Let me know if you have any other questions. Gracias!

Yes, these are the correct branches. v2 and ps6 branches don't support Durable officially, so this fix is not applicable there anyway. Muchas gracias!