chore(core): drop the unused VOS_VERSION constant from compiled output

[hblee12294]

Every compiled module opened initVos with const VOS_VERSION = <n>; and nothing ever read it — not the runtime, not the bridge, not any consumer. This removes the emit, and with it the version local that existed only to interpolate into it.

The config's version field is untouched and stays load-bearing: it is the discriminator migrateConfig reads to upgrade older configs, and a required field on vosConfigJsonSchema. Only the dead emit goes.

Diff

 export const initVos = async (container, deps) => {
-  const VOS_VERSION = ${version};
   const { THREE, gsap, resolution } = deps;

Verification

• pnpm build, pnpm typecheck, pnpm lint, pnpm test all pass repo-wide (150 core tests, unchanged from the baseline on main; typecheck matters here because dropping the emit would otherwise leave version unused).
• Compiled a config against the built package on both tween backends (vos and gsap): VOS_VERSION is absent and the emitted module still parses as valid JS.
• Confirmed by grep that nothing in this repo referenced the constant.

Compiled output bytes shift by one line for every config, so downstream committed build artifacts want a regenerate on the next engine bump.