feat(wash-lib)!: add support for inspecting wit

[brooksmtownsend]

Feature or Problem

This PR allows wash users to add --wit after or before their file/oci reference to print out the embedded wit world in a WASI preview 2 component. In the case that it is an empty wit world, it's assumed that it is a WASI preview 1 component and we output a message accordingly.

I also changed the heading from the claims inspect from Module to Actor and Provider Archive to Capability Provider. Keeping it as module just felt confusing when we'll be inspecting components too.

cargo run -- inspect wasmcloud.azurecr.io/echo:0.3.4      
    Finished dev [unoptimized + debuginfo] target(s) in 0.36s
     Running `/Users/brooks/github.com/wasmcloud/wasmCloud/target/debug/wash inspect 'wasmcloud.azurecr.io/echo:0.3.4'`

                                                                          
                               Echo - Actor                               
  Account       ACOJJN6WUP4ODD75XEBKKTCCUJJCY5ZKQ56XVKYK4BEJWGVAOOQHZMCW  
  Actor         MBCFOPM6JW2APJLXJD3Z5O4CN7CPYJ2B4FTKLJUR5YR5MITIU7HD3WD5  
  Expires                                                          never  
  Can Be Used                                                immediately  
  Version                                                      0.3.4 (4)  
  Call Alias                                                   (Not set)  
                               Capabilities                               
  HTTP Server                                                             
                                   Tags                                   
  None  

Related Issues

Related to #336

Release Information

wash-lib 0.16.0

Consumer Impact

This is a backwards compatible change in wash-cli, but consumers of wash-lib that are instantiating the full InspectCommand struct will need to add the wit boolean field.

Testing

Unit Test(s)

Acceptance or Integration

Manual Verification

Module

cargo run -- inspect wasmcloud.azurecr.io/echo:0.3.4 --wit                    
    Finished dev [unoptimized + debuginfo] target(s) in 0.38s
     Running `/Users/brooks/github.com/wasmcloud/wasmCloud/target/debug/wash inspect 'wasmcloud.azurecr.io/echo:0.3.4' --wit`

WIT World 'root' is empty, this looks like a WASI Preview 1 Module

Component

➜ cargo run -- inspect ~/demo/componentize-js/hello_s.component.wasm --wit 
    Finished dev [unoptimized + debuginfo] target(s) in 0.38s
     Running `/Users/brooks/github.com/wasmcloud/wasmCloud/target/debug/wash inspect /Users/brooks/demo/componentize-js/hello_s.component.wasm --wit`

package root:component;

world root {
  import wasi:io/error@0.2.0-rc-2023-11-10;
  import wasi:io/streams@0.2.0-rc-2023-11-10;
  import wasi:filesystem/types@0.2.0-rc-2023-11-10;
  import wasi:filesystem/preopens@0.2.0-rc-2023-11-10;
  import wasi:sockets/tcp@0.2.0-rc-2023-11-10;
  import wasi:cli/stdin@0.2.0-rc-2023-11-10;
  import wasi:cli/stdout@0.2.0-rc-2023-11-10;
  import wasi:cli/stderr@0.2.0-rc-2023-11-10;
  import wasi:cli/terminal-input@0.2.0-rc-2023-11-10;
  import wasi:cli/terminal-output@0.2.0-rc-2023-11-10;
  import wasi:cli/terminal-stdin@0.2.0-rc-2023-11-10;
  import wasi:cli/terminal-stdout@0.2.0-rc-2023-11-10;
  import wasi:cli/terminal-stderr@0.2.0-rc-2023-11-10;

  export wasmcloud:bus/guest;
}

[vados-cosmonic]

LGTM 🚀

[connorsmith256]

A couple in-line questions, and one here: I see updated tests for the default case, but not a test case for the new functionality. Shouldn't we have a new test for that?