componetize command does not export wasi:http/incoming-handler

I might be just doing something wrong, but here's a simple repro.

test.js
```
addEventListener('fetch', (evt) => {
console.log('fetch-event style request handling');
});
```

world.wit

its empty because all it wants to do is be an http server... (if I went wrong its probably here, I assume we don't have to manually export wasi:http/incoming-handler in our world)

```
package fetch:test;

world ui {
}
```

with jco 1.13

jco componetize handle.js --wit world.wit --out handle.wasm

which yields what I would expect, sands that ability to actually accept an incoing request.

all the other package definitions have been omitted, this is was I see when inspecting the component with the wit vs code extension.

```
package root:component;

world root {
import wasi:io/error@0.2.3;
import wasi:io/poll@0.2.3;
import wasi:io/streams@0.2.3;
import wasi:cli/stdin@0.2.3;
import wasi:cli/stdout@0.2.3;
import wasi:cli/stderr@0.2.3;
import wasi:cli/terminal-input@0.2.3;
import wasi:cli/terminal-output@0.2.3;
import wasi:cli/terminal-stdin@0.2.3;
import wasi:cli/terminal-stdout@0.2.3;
import wasi:cli/terminal-stderr@0.2.3;
import wasi:clocks/monotonic-clock@0.2.3;
import wasi:clocks/wall-clock@0.2.3;
import wasi:filesystem/types@0.2.3;
import wasi:filesystem/preopens@0.2.3;
import wasi:random/random@0.2.3;
import wasi:http/types@0.2.3;
import wasi:http/outgoing-handler@0.2.3;
}
```

most importantly, the component doesn't automatically export wasi:http/outgoing-handler like the big fat

would suggest....

Comece com a reprodução em test.js e world.wit e execute o comando jco componentize mostrado. Inspecione as importações e exportações WIT do componente gerado, concentrando-se no motivo pelo qual wasi:http/incoming-handler está ausente. Considera-se concluído quando o caso documentado de servidor HTTP produz um componente que expõe a interface incoming-handler esperada.

Escrita pelo modelo de indexação a partir do texto da issue.