feat: Implement component-model proposal in WasmEdge

[dannypsnl]

Summary

Component model is a wasm proposal that introduces a new binary format called component, the WASI Preview2 (#2939) is highly dependent on the format. Therefore, this issue tracks the implementation status of component model in WasmEdge.

Details

• parser
  • [Proposal] component model loading #3036
  • [loader] the unique_ptr at the place is not required #3149
  • [component model] wrong loading #3152
  • [component model] section order will affect index space #3202
  • [component model] a super minor bug #3341
  • [component model] Do despecialize when we load types #3349
  • [Component Model] Loader import and export name rules change #3741
• validator feat: component-model proposal's validation #3150 (2024/12)
  • [component model] the least needed validation #3179 (2024/01)
  • [Component] break down validation for most tasks #3619 (2024/08-10)
• executor feat: component-model proposal's instantiation #3151
  • [component model] instantiate #3218 (2024/06)
  • [Component] interface types #3380 (2024/07-10)
  • [component] instantiation of start section #3784 (2024/10)
  • [WASI] preview2 plugins, resource type instantiation, and related types export from plugin #3753 (2024/09-?)

Appendix

• versions:
  • cargo 1.77.0-nightly (3e428a38a 2024-01-09)
  • rustc 1.77.0-nightly (a2d9d73e6 2024-01-10)
  • cargo component 0.6.0 (205c6ee97 2023-12-22)
  • wasm-tools 1.0.57
• The book of component model: https://component-model.bytecodealliance.org/
• Test suites: https://github.com/second-state/component-model-tests
• refers to Component Model Use Cases Survey #1892
• The issue replace Implement component-model proposal in WasmEdge #1433

[dannypsnl]

command	explain
wasm-tools dump xxx.wasm	dump content of binary with explaintion
wasm-tools component new core.wasm -o component.wasm	wrap a wasm into component
wasm-tools component wit component.wasm	extract wasm types interface from a component binary