feat: support WasmEdge as an alternative engine

[xxchan]

Test:

# prepare the .wasm file
cd smartmodule/examples && make build

# run test
cd ../..
source $HOME/.wasmedge/env
cargo test -p fluvio-smartengine --features wasmedge-engine


running 8 tests
test engine::wasmedge::transforms::filter_map::test::test_filter_map ... ok
test engine::wasmedge::transforms::aggregate::test::test_aggregate_with_initial ... ok
test engine::wasmedge::transforms::filter::test::test_filter_with_init_invalid_param ... ok
test engine::wasmedge::transforms::map::test::test_map ... ok
test engine::wasmedge::transforms::filter::test::test_filter ... ok
test engine::wasmedge::transforms::aggregate::test::test_aggregate_ok ... ok
test engine::wasmedge::transforms::filter::test::test_filter_with_init_ok ... ok
test engine::wasmedge::transforms::array_map::test::test_array_map ... ok

[xxchan]

WasmEdge support completed in 7924834. All original tests passed. (Most code & tests are shared by both engines!)

Keep working on

• WasmEdge demo (e.g., TF)
• Try to split into smaller PR to be merged in upstream.

[sehz]

can you reorder terms in of:

• std
• third party
• fluvio dep

[xxchan]

That's OK. Are you going to review the PR now? I will resolve such issues if general ideas LGTY.

P.S. this PR is generally complete except minor points.

[sehz]

Can you split this into PR just related to without WasmEdge? We need to discuss how to maintain WasmEdge related code.

Thanks

[xxchan]

That's OK. But I'd like to elaborate a bit: only folder wasmedge is WasmEdge-specific code, and that's ~300 lines of simple code. To discuss how to maintain WasmEdge related code, and to get the ideas of how the common code work, it might be better to keep WasmEdge related code now. This can actually make it easier to review this PR.

I can remove the WasmEdge related code after the code review if that's not decided.

[sehz]

I would like have review by team but can't seem to add reviewers

[xxchan]

I created a PR to the main repo infinyon#3257