Wait for dispatched jobs to finish before moving on

[randy-coburn-zeam]

It would be great if we could wait for the downstream job to finish before moving on. This means we can use this action in deployments (like we do).
Also having the job reflect the output of the downstream job would be great since we can then report that the chain was broken.

I have put a PR together for this: #301

[Codex-]

The awaiting of a pending job can be completed using await-remote-run

The two tend to go hand-in-hand, but awaiting completions of dispatched runs using this action is not always desirable

The readme for this action does not mention this though, so I'll update that

[randy-coburn-zeam]

Thanks for showing me that.

This additional action does seem to do everything.

I'm not sure I understand the reasoning to split them into separate job when its very likely they will always be used together. The difference between waiting and not waiting could just be a bool option rather than an additional step.

I don't know if I am missing something, can you say why they are split?