refactor: remove unused exports data props

[bluwy]

Description

Some props of ExportsData are not used anymore with the current logic of needsInterop

I'd like to remove extractExportsData some day to simplify things, but it's still needed for:

1. Process .js as .jsx in dependencies
2. Needs interop check 😢

Additional context

---

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

Before submitting the PR, please make sure you do the following

• Read the Contributing Guidelines.
• Read the Pull Request Guidelines and follow the PR Title Convention.
• Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
• Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
• Ideally, include relevant tests that fail without this PR but pass with it.

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[bluwy]

I'm not sure if it's intentional, but this code mutates the global esbuildOptions config when using this function and hitting this code path. I've removed it as it should already be handled at

vite/packages/vite/src/node/optimizer/index.ts

Lines 729 to 736 in 0948803

	if (exportsData.jsxLoader && !esbuildOptions.loader?.['.js']) {
	// Ensure that optimization won't fail by defaulting '.js' to the JSX parser.
	// This is useful for packages such as Gatsby.
	esbuildOptions.loader = {
	'.js': 'jsx',
	...esbuildOptions.loader,
	}
	}

[patak-dev]

Nice one! Looking forward to a far future where we can delete the needs interop check 🥲