feat: custom registries for targets in cargo-component new

This commit adds support for using custom registries with targets when
performing `cargo component new`. Users can specify a registry URI
like `oci://ghcr.io` along with a registry namespace prefix like
`bytecodealliance` and get easy access to packages (e.g. `docs:adder`)
that are provided therein.

Signed-off-by: Victor Adossi <vadossi@cosmonic.com>

Author: vados-cosmonic

Cargo.lock

@@ -47,6 +47,7 @@ url = { workspace = true }
 wasi-preview1-component-adapter-provider = { workspace = true }
 wasm-metadata = { workspace = true }
 wasm-pkg-client = { workspace = true }
+wasm-pkg-common = { workspace = true }
 wasmparser = { workspace = true }
 which = { workspace = true }
 wit-bindgen-core = { workspace = true }
@@ -96,8 +97,8 @@ serde = { version = "1.0.197", features = ["derive"] }
 serde_json = "1.0.115"
 tempfile = "3.10.1"
 tokio = { version = "1.44.2", default-features = false, features = [
-    "macros",
-    "rt-multi-thread",
+  "macros",
+  "rt-multi-thread",
 ] }
 tokio-util = "0.7.10"
 toml_edit = { version = "0.22.9", features = ["serde"] }
@@ -109,7 +110,8 @@ warg-protocol = "0.9.0"
 warg-server = "0.9.0"
 wasi-preview1-component-adapter-provider = "29.0.1"
 wasm-metadata = "0.227.0"
-wasm-pkg-client = "0.9.0"
+wasm-pkg-client = "0.11.0"
+wasm-pkg-common = "0.11.0"
 wasmparser = "0.227.0"
 wasmprinter = "0.227.0"
 wat = "1.220.0"