Use Duckscript functions in Makefile.toml

[sffc]

In the WASM and Valgrind CI tools, we have some boilerplate that should be able to be refactored more cleanly into a Duckscript function.

Also, the way we loop over examples is better in Valgrind than in WASM, and we should use the Valgrind approach for both.

Suggested task list:

• Review the documentation for cargo make, the Duckscript language, and the Duckscript SDK.
• Review how our Makefile.toml currently works, including the imports from /tools/scripts, keeping an eye out for areas where we could reduce duplication or make things more efficient.
• Create a new Duckscript file to contain shared functions/routines.
• Refactor the code from valgrind.toml into a function called something like for_each_example that runs a loop over all examples.
• Re-write the wasm-wasm-dev and wasm-wasm-release tasks in wasm.toml using the new for_each_example function.
• Also in wasm.toml, refactor the loops in wasm-wat, wasm-dcmp, wasm-opt, and wasm-twiggy-dominators to use new function named something like for_each_stale_wasm.