fetsorn

Resolves #970. The Uri field in the workflow script has type `any` so that it is compatible with core's `TUri extends URI | String` type.

Based on #1100 Resolves #1131 - move workflow from core and client to cli - move workflow schema to polywrap manifest schemas

replace Option with Box | null in wasm

3

Optional base types are currently implemented as an Option container in `wasm-as` and `schema/bind`. But to omit optional fields from the function parameters we need a `| null` union type....

Workflow logic should reside in `cli`, and the workflow type should be imported from polywrap-manifest-types-js.

When wrappers are loaded and invoked, client should output logs to the console. Like this `[Polywrap] Wasm Wrapper Loaded: wrap://...` There already is a tracer for zipkin and opentelemetry which...

The Polywrap client has good foundations for tracing, but it needs better filters and easier setup. CLI should have a `polywrap trace` command, which would spin up a docker container...

Fixes #8

fix typo in req-query.md

1

`app.setting('query parser', ...)` should be `app.set('query parser', ...)`. same as #1361, but for both 4x and 5x @dougwilson

**Describe the bug** Polywrap failed validation of polywrap.yaml when I set `import_abis[0].abi` path to "./node_modules/@fetsorn/package". The error seems to occur only when the "at sign", "@" is in the path....

**Is your feature request related to a problem? Please describe.** rust bindings always have dead code and used variables, which throws unnecessary warnings during build. **Describe the solution you'd like**...