[Bug]: Unable to generate bindings for katei/irb

[Michael-F-Bryan]

What happened?

We found that the WAPM backend can't generate bindings for katei/irb version 0.1.0 due to some sort of error when looking up the irb atom in the *.webc file.

Steps to reproduce:

$ curl -O https://storage.googleapis.com/wapm-registry-prod/packages/katei/irb/irb-0.1.0.webc
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 40.4M  100 40.4M    0     0  5382k      0  0:00:07  0:00:07 --:--:-- 5861k

$ wasmer-pack show irb-0.1.0.webc
Error: Unable to load the package

Caused by:
    no "atom" or "wasi.atom" or "emscripten.atom" found in command Command {
        runner: "https://webc.org/runner/wasi/command@unstable_",
        annotations: {
            "wasi": Map(
                {
                    Text(
                        "atom",
                    ): Text(
                        "irb",
                    ),
                    Text(
                        "package",
                    ): Null,
                    Text(
                        "main_args",
                    ): Text(
                        "-I/pseudo/lib /pseudo/libexec/irb --prompt default",
                    ),
                },
            ),
        },
    }

It looks like this is an issue in wapm2pirita or the webc crate and we're hitting errors on this line.

The error looks similar to #96, but I don't think it's the same. In that ticket, we said the ABI was wasm4 (which WebC::get_atom_name_for_command() doesn't understand), whereas with this *.webc file, the annotations do have a wasi.atom field.

Wasmer Pack Version

wasmer-pack-cli 0.6.0

How were you using wasmer-pack?

wasmer run

CC: @ayys