`cargo component add` not producing runnable/usable binaries

Currently, `cargo component add` produces binaries using the `unlocked-dep` import syntax, which is not supported yet. Not runnable or parsable in today's tools. There are a number of things to figure out to get that feature supported, which I'd also like to move forward with.

I'm considering revising `cargo component add` behavior to produce binaries that can be used today.

Say you have a component package (an implementation not a pure `wit` package) that you'd like to use as a library in your component. `cargo component add example:library` would set you up with the bindings to use it. Then when you, `cargo component build`, the outputted binary includes the composed dependency and would be usable in current released tooling.