Webpack Public Path to import 'itk-vtk-viewer' downstream

[PaulHax]

To use the pre-built itk-vtk-viewer bundle as a upstream dependency we:

• Change Webpack's publicPath to '' (document relative) rather than the default auto. publicPath as auto caused a automatic publicpath is not supported in this browser error when including itk-vtk-viewer in the bundle.
• Lift itk-wasm's pipeline.worker.js to live at the same level as the bundle, so the document/worker.js relative publicPath still lets the worker find the .wasm files. Before, the theory is publicPath resolved to an absolute path, so .wasm files were found no matter pipeline.workers.js' location.

This change allows for a vite project to

import 'itk-vtk-viewer'
itkVtkViewer.createViewer(...

With a vite.config.js like this

import { fileURLToPath, URL } from 'url'
import { viteStaticCopy } from 'vite-plugin-static-copy'
import { defineConfig } from 'vite'

export default defineConfig({
  optimizeDeps: {
    include: ['itk-vtk-viewer'],
  },
  plugins: [
    viteStaticCopy({
      targets: [
        { src: 'node_modules/itk-vtk-viewer/dist/pipeline.worker.js', dest: '' },
        { src: 'node_modules/itk-vtk-viewer/dist/itk', dest: '' },
      ],
    }),
  ],

Still have to lift up the pipeline.worker.js and the .wasms =(

Inspired by #475

[LeviEyal]

Any idea when this branch will be released? It works great on my Vite app as described

[thewtex]

If I recall correctly, there were other deployment scenario's where this configuration needed to be verified and possibly did not work?

It may take some work to rebase this on HEAD. Instead, we will do better by migrating to itk-wasm 1.0, which is improving webassembly asset configuration to runtime-calls instead of the build-time configurations. ~1 month time frame.