Expand visible workbench scenarios to the full browser-safe set

[mkilijanek]

Problem
Workbench currently exposes too few scenarios compared to the actual browser-safe capability surface, and manual fixes are being added reactively.

Outcome
Expand the workbench catalog to a broad browser-safe scenario set and verify that every exposed operation can be added and executed without runtime faults.

Scope

• add the missing browser-safe codecs, text, network, and safe forensic operations to the visible catalog
• add a catalog sweep regression that validates add-step and run behavior for exposed operations
• keep browser-incompatible or Node-only operations out of the browser runtime
• update release and development docs with the supported workbench scenario surface