Better error for `performance` access at Wizer time

I still get the same error with jco 1.7.1 that uses 0.13.1 of this project. #150 does not set timeOrigin. The change from https://github.com/bytecodealliance/ComponentizeJS/pull/146/commits/cb4d73af4fbbd75fb4bafc79b04a7d500180bd96#diff-882dd8ad95be11b373fd2693a697c12144f8b51d4605a35cd678a0d2e5b4a09dR354 makes it work for me locally.

```
~/ms/StarlingMonkey15/cowsay> npx jco componentize cowsay.js --wit src/cowsay.wit -o cowsay.wasm
Redirecting call to abort() to mozalloc_abort

Error: the `componentize.wizer` function trapped

Caused by:
0: error while executing at wasm backtrace:
0: 0x25f20 - !
1: 0x25f29 - !
2: 0xa921 - !
3: 0x42119 - !
4: 0x25431f - !
5: 0x254f50 - !
6: 0x25576e - !
7: 0x35a029 - !
8: 0x258ee8 - !
9: 0x24bbcc - !
10: 0x245b22 - !
11: 0x255aeb - !
12: 0x29a0a9 - !
13: 0x34e9db - !
14: 0x34e72d - !
15: 0x20286 - !
16: 0x1f50e - !
17: 0xa882 - !
18: 0x22580f - !
1: wasm trap: wasm `unreachable` instruction executed
(jco componentize) Error: Failed to initialize the compiled Wasm binary with Wizer:
Wizering failed to complete
at componentize (file:///Users/cataggar/ms/StarlingMonkey15/node_modules/@bytecodealliance/componentize-js/src/componentize.js:271:13)
at async componentize (file:///Users/cataggar/ms/StarlingMonkey15/node_modules/@bytecodealliance/jco/src/cmd/componentize.js:11:25)
at async file:///Users/cataggar/ms/StarlingMonkey15/node_modules/@bytecodealliance/jco/src/jco.js:200:9
```

Reproduce the failure with the jco componentize command, cowsay.js, and src/cowsay.wit, then inspect the componentize.js call at line 271 in the reported stack. Compare the referenced ComponentizeJS PR #146 change and issue #150, focusing on performance access during Wizer initialization. Done means the example componentizes without the componentize.wizer trap.

Written by the indexing model from the issue text.