fix(optimizer): ignore EACCES errors while scanner (fixes #8916)

[sapphi-red]

Description

#8916 happens with 2.9.x. But it works with 3.x.x (the error message is present though). I think changes around the scanner affected this.

About Vite 3, the error is thrown from discoverProjectDependencies and catched here. So I assume the optimizer won't run and the deps will be stuck instead of all js files?

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

Lines 190 to 227 in 1983cf4

	// Ensure server listen is called before the scanner
	setTimeout(async () => {
	try {
	debug(colors.green(`scanning for dependencies...`))
	const deps = await discoverProjectDependencies(config)
	debug(
	colors.green(
	Object.keys(deps).length > 0
	? `dependencies found by scanner: ${depsLogString(
	Object.keys(deps)
	)}`
	: `no dependencies found by scanner`
	)
	)
	// Add these dependencies to the discovered list, as these are currently
	// used by the preAliasPlugin to support aliased and optimized deps.
	// This is also used by the CJS externalization heuristics in legacy mode
	for (const id of Object.keys(deps)) {
	if (!metadata.discovered[id]) {
	addMissingDep(id, deps[id])
	}
	}
	if (!isBuild) {
	const knownDeps = prepareKnownDeps()
	// For dev, we run the scanner and the first optimization
	// run on the background, but we wait until crawling has ended
	// to decide if we send this result to the browser or we need to
	// do another optimize step
	postScanOptimizationResult = runOptimizeDeps(config, knownDeps)
	}
	} catch (e) {
	logger.error(e.message)
	} finally {

This PR fixes the error.

fixes #8916

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 Commit 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.

[patak-dev]

I don't see a way around this, even if this means potentially hiding some useful errors. It could be interesting in the future to see if we could only suppress EACCESS errors and not other types but this should be a feature of fast-glob IIUC