Make stdout from non-script steps available as an output

[crenshaw-dev]

Summary

There have been a couple requests for making stdout available as an output for non-script steps.

Wrapping the container to pipe stdout to a file or refactoring to use a script step both feel hacky.

Motivation

When I don't have control of or don't want to modify an image to access stdout as an output.

The hacks/workarounds are simple enough. But adding this feature would reduce some (apparently common) onboarding friction, since people seem to expect stdout to be available on outputs.result.

Proposal

I think outputs.result should contain the stdout.

---

Message from the maintainers:

If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.

[alexec]

How do we deal with large amounts of output?

[alexec]

@simster7 to close if done

[simster7]

Closed by #2584