When reviewing a pipeline's output, it's difficult to determine which stages we control and which we don't. Lots of additional stages are injected by required pipeline templates.

We should add some logic to inject a common prefix to each task/step's displayName. Something simple that stands out is an emoji like 🟪. (purple because that's .NET's color).

One problem that I see with this approach is that the postPublishNotification ImageBuilder command relies on the displayName of tasks to check if they were successful.

That behavior should be based on the name of the steps, not the displayName. That way we can do whatever we want with displayNames without worrying about breaking publish notifications.