fix(worker): string interpolation in dynamic worker options

[christoph-pflueger]

Description

Fixes a bug that unintentionally removes the backtick and comma at the end of a template literal in dynamic worker options.

Test failure without fix:

 FAIL  packages/vite/src/node/__tests__/plugins/workerImportMetaUrl.spec.ts > workerImportMetaUrlPlugin > with interpolated dynamic name field and static type in worker options
RollupError: Unexpected eof
 ❯ getRollupError node_modules/.pnpm/[email protected]/node_modules/rollup/dist/es/shared/parseAst.js:396:41
 ❯ convertProgram node_modules/.pnpm/[email protected]/node_modules/rollup/dist/es/shared/parseAst.js:1084:26
 ❯ parseAstAsync node_modules/.pnpm/[email protected]/node_modules/rollup/dist/es/shared/parseAst.js:2070:106
 ❯ parseWorkerOptions packages/vite/src/node/plugins/workerImportMetaUrl.ts:105:8
    103|   } catch {
    104|     const optsNode = (
    105|       (await parseAstAsync(`(${rawOpts})`))
       |        ^
    106|         .body[0] as RollupAstNode<ExpressionStatement>
    107|     ).expression
 ❯ getWorkerType packages/vite/src/node/plugins/workerImportMetaUrl.ts:169:22
 ❯ Object.transform packages/vite/src/node/plugins/workerImportMetaUrl.ts:239:30
 ❯ packages/vite/src/node/__tests__/plugins/workerImportMetaUrl.spec.ts:14:20
 ❯ packages/vite/src/node/__tests__/plugins/workerImportMetaUrl.spec.ts:96:7

[christoph-pflueger]

Is it even necessary to strip the trailing comma? The tests seem to pass with the comma present as well.

[sapphi-red]

Is it even necessary to strip the trailing comma? The tests seem to pass with the comma present as well.

It was needed because we were not using parseAstAsync in the past. Now it works without stripping the trailing comma as we fallback to parseAstAsync when evalValue failed. But since evalValue is more faster, I think we can keep stripping the trailing comma and avoid fallbacking back in this case.

[sapphi-red]

Thanks!