fix: wasm_opt

[ChenKS12138]

1. As @PiotrSikora says, in order to runwasm_opt, a dynamic library needs to be installed (for Linux and mac os). Update wasm-opt to version_97. #91 (comment)
   And the cache folder's structure will be as follow.

2. update wasm_opt version from version_97 to version_105

[ChenKS12138]

Oops, some checks are stills be not successful, IMHO maybe examples/markdown is not a suitable example for cargo-wasi, we need to remove it, as @alexcrichton says

the wasm32-wasi target is not compatible with wasm-bindgen

rustwasm/wasm-bindgen#2554 (comment)

Or, we should allow users to pass and override the target argument, something like that. (It works well to compile examples/markdown if I have changed the target)

cargo wasi build -p markdown --release --verbose --target wasm32-unknown-unknown

cargo-wasi/src/lib.rs

Lines 82 to 94 in 6d2e502

	// TODO: figure out when these flags are already passed to `cargo` and skip
	// passing them ourselves.
	cargo.arg("--target").arg("wasm32-wasi");
	cargo.arg("--message-format").arg("json-render-diagnostics");
	for arg in args {
	if let Some(arg) = arg.to_str() {
	if arg.starts_with("--verbose") || arg.starts_with("-v") {
	config.set_verbose(true);
	}
	}
	cargo.arg(arg);
	}

[ChenKS12138]

1. As @PiotrSikora says, in order to runwasm_opt, a dynamic library needs to be installed (for Linux and mac os). Update wasm-opt to version_97. #91 (comment)
   And the cache folder's structure will be as follow.

2. bump wasm_opt version from version_97 to version_105

3. Installing target wasm32-unknown-unknown when compiling example/markdown on CI.

[alexcrichton]

Sorry there's a good number of changes here and I don't have a ton of time to review this right now. If wasm-opt-the-builtin-version isn't working well I'd recommend disabling it and then manually running it afterwards.

[ChenKS12138]

I have removed the code that updating wasm-opt version, and I believe this is the minimum code changes to let CI checks pass.

There is no problem with wasm-opt-the-builtin-version, but an essential library (libbinaryen.dylib/libbinaryen.a) is not installed and linked.