fix: shipped modules do not depend on wippy/test

[wolfy-j]

Cause

Ten shipped modules declared wippy/test as a dependency because their test entries lived in the shipped tree. Every application that installed one of them also installed wippy/test and its wippy/terminal, and shipped their test entries.

Change

• In bootloader, migration, embeddings, usage, agent, llm, facade, relay, actor and views:
  • test entries and their Lua files move into each module's test workspace;
  • test-only helpers move with them: agent.tools:delay_tool, views:page_access_probe and views:test_page_view_policy;
  • each test workspace declares dep.wippy.test.
• The shipped modules drop dep.wippy.test, the depends_on: ns:wippy.test references, and lock pins that existed only for test/terminal.
• actor gets a test _index.yaml, and its test workspace points at ...
• Name clashes in test workspaces are resolved by renaming the existing entries:
  • facade config_handler_test becomes config_dependency_test;
  • views component_registry_test becomes component_registry_regression_test.
• facade's shipped security_policy_test is removed. The test workspace already ran the same assertions, and that copy now has the shipped copy's types.

Verification

Each test workspace was checked before and after with wippy lint --level error and make test:

module	tests before	tests after
bootloader	22	22
migration	25	25
actor	21	21
usage	6	6
agent	371	371
llm	1555	1555
facade	75	74 (duplicate removed)
relay	19	19
views	95	95
embeddings	boot fails (no such module: vec0, sqlite extension missing locally)	same

• Lint is clean in every workspace.
• scripts/check_module_manifests.py passes.
• The postgres targets were not run.