Core: Fix sorting by __namedExportsOrder

[shilman]

Issue: #15574

What I did

Story sorting has changed completely in 6.4, and the old code that handled __namedExportsOrder is broken. I'm not even sure if we need it anymore @tmeasday

Instead:

• Fix v6 handling in StoryStoreFacade
• Fix v7 handling in the story index by updating CSFFile

How to test

See attached tests & updated examples

[nx-cloud]

Nx Cloud Report

CI ran the following commands for commit 0787dfc. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

Status	Command
	nx run-many --target=prepare --all --parallel --max-parallel=15

---

Sent with 💌 from NxCloud.

[tmeasday]

This LGTM but should we remove the code from processCSFFile which (uselessly) considered __namedExportsOrder? :

storybook/lib/store/src/processCSFFile.ts

Lines 51 to 61 in 088ea76

	// prefer a user/loader provided `__namedExportsOrder` array if supplied
	// we do this as es module exports are always ordered alphabetically
	// see https://github.com/storybookjs/storybook/issues/9136
	if (Array.isArray(__namedExportsOrder)) {
	exports = {};
	__namedExportsOrder.forEach((name) => {
	if (namedExports[name]) {
	exports[name] = namedExports[name];
	}
	});
	}

[shilman]

@tmeasday yes but I wasn't sure what impact that would have. trying it now.

[shilman]

self-merging @tmeasday