Plugins that contain views don't resolve yet

Given the following plugin with the module path plugin.com

bud-admin/
  view/
    index.svelte
plugin.go
go.mod

And an application with the following module path app.com, if you run bud build, you'll get the following:

ssr_test.go:293: err: conjure: generate "bud/view/_ssr.js" > ✘ [ERROR] Could not resolve "./view/index.svelte"

svelte:./bud/view/index.svelte:2:28:
	2 │ import ViewIndexSvelte from "./view/index.svelte"
		╵                             ~~~~~~~~~~~~~~~~~~~~~

I assume this error is because ESBuild doesn't yet support virtual file paths, so it's one of the few places in the codebase where we rely on the underlying filesystem. The actual location of the index view is in the plugin.com module's view/ not your app.com's view/.

If that's the case, the ESBuild resolver should be updated to use the virtual filesystem.

Start with ssr_test.go:293 and the bud build path that produces bud/view/_ssr.js; inspect how plugin.com's view/index.svelte is resolved versus app.com's view. Update the ESBuild resolver to use the virtual filesystem, then rerun the failing SSR build case and confirm plugin views resolve.