Prepare for new release

[jprendes]

This PR:

• bumps the crate versions to 0.13.0
• adds a missing description to the hyperlight-wasm-runtime crate, which is required by crates.io
• use cargo-overlay-registry so that we can dry-run the crate publishing

Regarding the last item, since we have interdependent crates in the repo, when we dry-run the hyperlight-wasm-runtime, it needs the hyperlight-wasm-macro crate, but the hyperlight-wasm-macro crate hasn't been published yet, so we can't dry-run it as a standalone crate, i.e., the following will allways fail:

cargo publish -p hyperlight-wasm-runtime --dry-run

A solution is to use workspace publishing, where you can specify more than one package to publish. This is stable since cargo 1.92 (IIRC), so we could do:

cargo publish -p hyperlight-wasm-runtime -p hyperlight-wasm-macro --dry-run

The same would apply to hyperlight-wasm, we would need to dry-run the 3 crates together.

The way that cargo makes this work is using an internal overlay registry, located in ./target/package/tmp-registry where it temporarely publishes the crates, and uses some internal mechanism to use that overlay registry during verification.

HOWEVER, as we are invoking cargo again from our buildscript in hyperlight-wasm, that internal mechanism to use the overlay registry is lost, and the cargo we invoke can't find the correct crate because it hasn't been published yet.

This PR works around that issue using the cargo-overlay-registry crate so that the child cargo also sees the tmp-registry created by cargo publish.

[jprendes]

@dblnz PTAL

[dblnz]

LGTM!