Originally reported by dayle.parker 

We support linking one quickstart to another via the `nextQuickStart` link array in the quickstart yaml spec. Each array entry points to another quickstarts metadata.name.

It was noticed however that these links are not actually rendering in the UI (see screenshot).

Since our quickstarts provider renders frequently and is available on any page, we improved the performance by only fetching all the data for the one active quickstart. However this breaks the nextQuickStart link logic as Patternfly expects the target quickstart of the link to be loaded/present in the array passed to the component.

We can fix this by fetching the quickstarts referenced in the `nextQuickStart` links array and passing them into patternfly.

Where we pass in quickstarts to patternfly: https://github.com/RedHatInsights/insights-chrome/blob/master/src/components/RootApp/RootApp.tsx#L83-L93 

Relevant patternfly code: https://github.com/patternfly/patternfly-quickstarts/blob/main/packages/module/src/QuickStartPanelContent.tsx#L63 

Slack thread context: https://redhat-internal.slack.com/archives/C05KTHJU4R4/p1759253892851009