Remove sync code from runc shim

[mxpv]

Closes: #134

[mxpv]

@jsturtevant any ideas why windows integration tests fail? Not sure I get what exactly wrong with it and I don't have windows env to verify (this also fails in main).

error[E0432]: unresolved import `ttrpc::asynchronous`
  --> crates\shim-protos\src\lib.rs:93:20
   |
93 |     pub use ttrpc::asynchronous::Client;
   |                    ^^^^^^^^^^^^ could not find `asynchronous` in `ttrpc`

[jsturtevant]

looks like bringing in the async feature somehow. I will take a look today.

this also fails in main

Looks like main is failing due to #160?

[mxpv]

Let me rebase this and give it another try.

[jsturtevant]

rebase didn't help 😞.

CI on main is passing today: https://github.com/containerd/rust-extensions/actions/runs/5743079375 and I was able to run the integration test locally on main. Going to pull this PR to see I can track down what is causing the mix up

[jsturtevant]

Still tracking down what is happening but cargo build -p containerd-shim-protos and cargo build -p containerd-shim builds fine on windows.

but cargo build --example skeleton fails with message error: could not compile containerd-shim-protos (lib) due to 117 previous error

[jsturtevant]

@mxpv I don't know why but it seems the examples are getting the feature=async enabled on them after the changes in this PR. Maybe the changes in the runc crate are causing the compiler/cargo to pick that up by default?

If I run cargo build --example skeleton -p containerd-shim then this works. So the fix would be to add -p containerd-shim and -p containerd-shim-protos to the cargo calls in:

rust-extensions/.github/workflows/ci-windows.yml

Lines 97 to 99 in 27a503a

	cargo run --example skeleton -- -namespace default -id 1234 -address "\\.\pipe\containerd-containerd" -publish-binary ./bin/containerd start
	ps skeleton
	cargo run --example shim-proto-connect \\.\pipe\containerd-shim-17630016127144989388-pipe

[mxpv]

@jsturtevant That did the trick!

[jsturtevant]

LGTM