Support granular secretness on invoke result properties

[mikhailshilkov]

Hello!

• Vote on this issue by adding a 👍 reaction
• If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

When an invoke returns a result with multiple properties and only one of them is marked as a secret, we currently have to "secretify" the entire result, because most SDKs return an Output<InvokeResult> where InvokeResult is plain. However for YAML, from the consumer point of view, this is not a requirement and may be unexpected - there is no type constraint that would prevent us from returning a mixed bag. Yet, we use the Go SDK behind the scenes, so secretness of a single property contaminates the entire result in YAML.

Affected area/feature

Invokes/Functions