Feature/mi 246 retain relative path for bundled handlers

[tvhees]

I'm not sure we'll need this but I think it's cleaner than expecting everything to be dumped in dist, especially when resolving the paths within a service.

Optionally we can also keep the /handlers/ folder but I don't see us bundling non-lambda code..

I've also moved the resolver functions below the service stack as that's the most important part of a service.

[kai-nguyen-aligent]

I don't see any change in term of logic around where the output is. However, I think this looks much cleaner than my original code.

[tvhees]

I don't see any change in term of logic around where the output is. However, I think this looks much cleaner than my original code.

Previously this

src/
    runtime/
         handlers/
              fetch-products.ts
              backend/
                  fetch-products.ts
              erp/
                  fetch-products.ts

would be built to

dist/
    fetch-products/
            index.mjs

with the most nested file winning, based on my limited testing

Now it will build to this:

dist/
    fetch-products/
        index.mjs
    backend/
        fetch-products/
            index.mjs
    erp/
        fetch-products/
            index.mjs

It's probably rare we'll have exactly the same file names, but being able to group handlers by folder is useful sometimes and I think this is a more predictable output structure.

[kai-nguyen-aligent]

You're right. I forgot to check the nested folder cases.