Doc: Explain how to chain launch plans

[fg91]

Why are the changes needed?

We currently don't provide an example for launch plan chaining in the docs and users asked me about this.
See added example in flyteorg/flytesnacks#1783.

• I updated the documentation accordingly.
• All new and existing tests passed.
• All commits are signed-off.

Related PRs

flyteorg/flytesnacks#1783

Docs link

[flyte-bot]

Code Review Agent Run Status

• Limitations and other issues: ❌ Failure - The AI Code Review Agent skipped reviewing this change because it is configured to exclude certain pull requests based on the source/target branch or the pull request status. You can change the settings here, or contact the agent instance creator at [email protected].

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 58.48%. Comparing base (a2331bd) to head (1ddb7a5).

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #6317      +/-   ##
==========================================
- Coverage   58.50%   58.48%   -0.02%     
==========================================
  Files         937      937              
  Lines       71088    71088              
==========================================
- Hits        41587    41577      -10     
- Misses      26349    26359      +10     
  Partials     3152     3152              

Flag	Coverage Δ
unittests-datacatalog	59.06% <ø> (ø)
unittests-flyteadmin	56.27% <ø> (-0.03%)	⬇️
unittests-flytecopilot	30.99% <ø> (ø)
unittests-flytectl	64.70% <ø> (-0.06%)	⬇️
unittests-flyteidl	76.12% <ø> (ø)
unittests-flyteplugins	61.00% <ø> (ø)
unittests-flytepropeller	54.79% <ø> (ø)
unittests-flytestdlib	64.04% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.