Fixed component lookup for shared/svelte/page.svelte

[NJKode]

Say you have a component with the following file structure:

[component-folder]
└── nested
    └── component
        ├── component.svelte
        └── component.bookshop.yaml

And the following object in your SvelteKit route:

component: {
  "_bookshop_name": "nested/component"
  "component_key": "component_value"
}

You should be able to render this using <Bookshop {...component} />.

However, Bookshop trips up due to the fact that the component is within a folder (nested/). Bookshop will look for the file [component-folder]/component/nested/component/nested.svelte, which does not exist.

The fix is to use the existing getComponentKey() function.