Launch "dry run" to render to commands without running any

Description

Render/print a launchfile with as much detail as possible given the context, without starting any processes

See https://github.com/ijnek/launch_graph which is trying to do a visualization side of this same consideration

Really this may be an extension of ros2 launch --print that just gets some more information, perhaps makes some more assumptions

Motivation

It can be unclear what the total outcome of a launchfile will be, and the logs that go by are too detailed to see what all the running nodes are.

This would allow for detailed inspection of what exactly launching a launchfile would do, without having to do it.
It also has the side effect of checking for file correctness.

Design / Implementation Considerations

I think it's a reasonable expectation that this does as much as it can given the current context - if an included file can't be found then that's all the info we get for example. But in a real environment, the leafs of the launch tree (nodes, commands) would be printed exactly as they would be run.

Additional Information

No response

Start by reviewing the existing ros2 launch --print behavior and the launchfile rendering path; no specific files or tests are named in the issue. Compare the proposed output with launch_graph and determine how much of the launch tree can be resolved without starting processes. Done means a dry-run command renders the available leaf nodes and commands without running them, while handling missing included files as described.