refactor: use rollup hashing when emitting assets

[patak-dev]

Done: This PR depends on rollup/rollup#4712, Rollup 3.3 includes it and we updated it in a separate PR.

Description

Rollup 3 has a new hashing algorithm that fixes the issues we had when emitting assets before:

• [v3.0] New hashing algorithm that "fixes (nearly) everything" rollup/rollup#4543

We currently do our own hashing and deduplication, see:

    // emit as asset
    // rollup supports `import.meta.ROLLUP_FILE_URL_*`, but it generates code
    // that uses runtime url sniffing and it can be verbose when targeting
    // non-module format. It also fails to cascade the asset content change
    // into the chunk's hash, so we have to do our own content hashing here.
    // https://bundlers.tooling.report/hashing/asset-cascade/
    // https://github.com/rollup/rollup/issues/3415

This is the first PR in a series to try to move back some of the responsibilities to Rollup. This should help to be compatible with external plugins using emitFile or config settings like assetFileNames. There was actually a faulty test in workers that was not letting us see a bug for workers and assetFileNames.

Ideally, we should try to move to also use import.meta.ROLLUP_FILE_URL_referenceId instead of our __VITE_ASSET__hash__. I still don't know if it is feasible though because we still need our own scheme for references in CSS. This PR already moves from our own hash to using referenceId though, and future PRs may move us closer to at least using rollup's scheme in JS files.

---

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

[benmccann]

SvelteKit and Rollup have one file naming scheme, but Vite has a different file naming scheme for inserting the hash into the file names (I don't recall the difference exactly, but think it was something like - vs . for separating the name and hash in the filename). It would be nice if Vite were able to align with Rollup as part of this as it would allow for a minor simplification in the Vite PWA codebase.

[patak-dev]

@benmccann we are using name.[hash].[ext] for JS, CSS, assets, while the default for both rollup and esbuild is name-[hash].[ext]. I'll check with the team what was the rationale here, it may just be historical and I agree this is a good opportunity to align with rollup. It would probably be done in a different PR though.

[sapphi-red]

Some nitpicks but other looks good to me!

[userquin]

I don't recall the difference exactly, but think it was something like - vs .

Here the entry: https://github.com/vite-pwa/sveltekit/blob/main/src/config.ts#L53

This will go to Vite 4? We can break existing plugins, at least Vite PWA, we're forcing to detect Vite version?

EDIT: PR sent to PWA Plugin to support both layouts, also sent PR to kit integration to remove it