Task: Remove the workspace from every trading entity

No trading entity carries a workspace, as the trade shape design decided when sandboxes replaced workspaces.

• No trading model, field group or profile it binds declares has_workspace_id or a workspace_id column; no trading table has the column.
• The ORE import, export and round trip behave as before.
• Build, ctest, pgTAP and the local check set pass.

Section 13 of the trade shape design removed workspaces from trading, and sandboxes and virtual books replaced them. The workspace column comes from the generator, so the change is to the models and profiles.

• The trading-instrument and trading-record profiles, which only trading binds, set has_workspace_id false.
• lifecycle_event moves from workspace-scoped-lookup, which refdata shares, to simple-lookup, its twin without a workspace.
• bond_issue drops its own flag, and the four identity field groups drop their workspace_id column.
• drop_trading_workspace_prose.py rewrites the model prose that described the workspace and drops the workspace filter from the pasted queries of the wide trade and the swap leg.
• The rest of the system keeps its workspaces until Remove workspaces from every component.

Every number this task claims about a tree, with the command that produced it and the commit it was measured at. A number without both is not a measurement, because a clean-up record describes a tree and trunk moves under a branch: a consumer count, a gate's component count and a suite's size all change with no code changing, and the reader of a bare number cannot tell which tree it came from. Where the raw output matters, put it in an evidence/ file beside the task and name that file in the Command column.

• The hand-maintained class diagrams of ores.trading.api and ores.trading.core still show workspace_id members; they were already behind the models before this task (trade_portfolio and the netting identifiers are missing too). Refreshing them is its own piece of work.

Manual QA scenarios (scaffolded via compass add test_scenario) that verify this task. Link new ones here as they're created; the scenario doc itself links back via its "Verifies task" field.

No trading table carries a workspace. The trading profiles, the identity field groups, bond_issue and lifecycle_event no longer declare one, and the regenerated tables, repositories, generators and protocols drop it. The ORE import, export and round trip read as before.