TOML and JSON formulas accepted `metadata = { ... }` on a step
without error, but the field was silently dropped:
- `formula.Step` had no `Metadata` field, so the TOML/JSON parsers
discarded the table during decode.
- `processStepToIssue` built the template issue with no metadata.
- `cloneSubgraph` omitted `Metadata` when spawning the mol/wisp,
so even if the template carried it, the poured bead did not.
Add `Step.Metadata map[string]interface{}` so the parser keeps the
table, marshal it to JSON in `processStepToIssue`, and copy the raw
bytes through in `cloneSubgraph`. `bd cook` now shows `metadata`
under each step, and `bd mol pour` / `bd mol wisp` land the bead
with the declared keys.