[Fix #1071] Until option if any is empty

[fjtirado]

Fix #1071

Please specify parts of this PR update:

• Specification
• Schema
• Examples
• Extensions
• Use Cases
• Community
• CTK
• Other

Discussion or Issue link:

What this PR does:

Additional information:

[cdavernas]

Can I ask you to update this sample by removing the now useless until: '${ false }' condition?

[fjtirado]

@cdavernas If no until, I guess the assumption (according to ther examples where any is not empty and there is no unitil) is to move forward when any event is received (in other words, no until is equivalent to until: ${true}, so the until you are requesting to remove is actually needed so is forever listening (aligned with the example file name)

[cdavernas]

@fjtirado Not as far as I understand it. If you define an empty any and do not define until, the task will listen for events forever.
Unless, of course, you'd want to say that defining an empty any will listen to the first consumed event, whatever it is, and then keep on. If so, which is a feature that I'm obviously not opposed against, I think that we need to add a new info block to the listen task, explaining the result of the different strategies. Also, adding a new example listening to one single 'any' event would then be required.

[fjtirado]

@cdavernas I prefer this because is aligned with the behaviour of other examples where there is at least one filter in the any array and there is no until. In those examples, once the expected event arrive, it moves forwards to next task. I think it should be the same when it is listening to all events.
Therefore, I will add the example and the explanation.

[cdavernas]

LGTM! Cheers man! ❤️

[ricardozanini]

Much easier to implement now! I'll remove the workarounds from the Go SDK hehehe