fix: needs es interop check for newly discovered deps

[patak-dev]

Description

This PR fixes the needs es interop check for newly discovered dependencies. It is an edge case, and this is why we didn't discover it so far. What needs to happen is that:

• There is a missing dependency that needs es interop
• and when re-processing the deps there is no need for a full-page reload.

And CI is going to fail for react-emotion because when we call moduleGraph.invalidateAll() before doing the full-reload after re-processing, there are requests that are on the fly and end up updating their module info... so when the browser requests them after the full reload... these modules are stale. @vursen this is what we were seeing in Vaadin with the 504 errors in the browser that didn't disappear even when reloading the page manually.

We need that a full-reload call will also stop every currently processing request to avoid modifying the module graph.

I think this could have been also present before, but now it is more visible because we aren't blocking the requests as before while processing. So a solution here may fix hard-to-replicate issues that we got in the past.

I'll work on a PR to fix the race condition next, I'm sending this PR to serve as a bug reproduction once CI fails.

---

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

[patak-dev]

fa88544 failed as expected

db17172 fixes the race condition described in the description by avoiding caching the transform result of a module that was invalidated while processing

Once we approve this PR as a whole, I can create a PR for the race condition fix and then merge this one.

[patak-dev]

Here is a run of Vite Ecosystem CI against this PR:
https://github.com/vitejs/vite-ecosystem-ci/actions/runs/1961459259

All green (except an expected vite-plugin-ssr fail which is also present in main right now)