PeterD1524

PR (WIP): https://github.com/WasmEdge/WasmEdge/pull/3499

PR for [WASI-NN Rust SDK](https://github.com/second-state/wasmedge-wasi-nn/tree/ggml/rust): https://github.com/second-state/wasmedge-wasi-nn/pull/15

#3499 is it still in the WIP stage.

Week 1 Summary - Created main PR - https://github.com/WasmEdge/WasmEdge/pull/3499 - added backend structure - Created PR for wasmedge-wasi-nn to support the new Piper backend - https://github.com/second-state/wasmedge-wasi-nn/pull/15

Week 2 Summary - Main PR - Fixed minor stuff - Added tests and build workflow - Created PR in [second-state/WasmEdge-WASINN-examples](https://github.com/second-state/WasmEdge-WASINN-examples) for example usage - https://github.com/second-state/WasmEdge-WASINN-examples/pull/145 - Created PR in...

Week 3 Summary - Main PR - Fixed minor stuff - Fixed some docs in [WasmEdge/docs](https://github.com/WasmEdge/docs) - https://github.com/WasmEdge/docs/pull/239

Week 4 Summary - main PR - Improved code for input validation - Resolved build issue - Merged

I just realized that Piper just downloads `libonnxruntime.so` and links to it, so `libwasmedgePluginWasiNN.so` doesn't work on its own. It looks like there is no easy option to toggle this...

> Should we follow the same procedure for downloading `libonnxruntime.so` for users? Can we ship `libonnxruntime.so` with `libwasmedgePluginWasiNN.so` together in the `WasmEdge-plugin-wasi_nn-piper.tar.gz`. I don't know if that is a good...

@hydai I opened a PR to fix the dependency problem: https://github.com/WasmEdge/WasmEdge/pull/3583