Componentize Debug Builds

[MendyBerger]

First: Thanks for this amazing project! I've been using it a lot lately and it's really a joy!

I'd love to be able to get debug builds out of Jco. I've ran into multiple cases where the wasm was crashing with unhelpful stack traces, and narrowing down the problem was extremely hard.

For example:

    0: error while executing at wasm backtrace:
           0: 0x593501 - <unknown>!<wasm function 10295>
           1: 0x2330ee - <unknown>!<wasm function 5297>
           2: 0x261016 - <unknown>!<wasm function 5562>
           3: 0x261c47 - <unknown>!<wasm function 5565>
           4: 0x262465 - <unknown>!<wasm function 5568>
           5: 0x366d22 - <unknown>!<wasm function 7374>
           6: 0x265bdf - <unknown>!<wasm function 5596>
           7: 0x2588c3 - <unknown>!<wasm function 5561>
           8: 0x252819 - <unknown>!<wasm function 5559>
           9: 0x260edc - <unknown>!<wasm function 5562>
          10: 0x261c47 - <unknown>!<wasm function 5565>
          11: 0x34f3a9 - <unknown>!<wasm function 7280>
          12: 0x261016 - <unknown>!<wasm function 5562>
          13: 0x261c47 - <unknown>!<wasm function 5565>
          14: 0x2e27af - <unknown>!<wasm function 6558>
          15: 0x31f3eb - <unknown>!<wasm function 6955>
          16: 0x2d7cb - <unknown>!<wasm function 398>
          17: 0x231c70 - <unknown>!<wasm function 5289>
          18: 0x7abd4f - <unknown>!wasi:cli/[email protected]#run
    1: wasm trap: wasm `unreachable` instruction executed

My understanding from here and here is that a debug build would give better track traces, and hence help with tracking down these kinds of crashes.