fix(fabric): restore ignores for legacy .paperclip state

[DeployFaith]

Motivation

• Recent namespace migration replaced .paperclip ignores with .fabric, leaving legacy Paperclip runtime state unignored and able to enter Docker build contexts or be accidentally committed.
• Legacy .paperclip/.paperclip-local directories may contain config, .env, DB files, tokens, or keys and should be denied from both git and Docker contexts as a defensive measure.

Description

• Added .paperclip and .paperclip-local to apps/fabric/.dockerignore to exclude legacy Paperclip runtime state from Docker build contexts.
• Added .paperclip/ and .paperclip-local/ to apps/fabric/.gitignore to make accidental commits of legacy Paperclip state less likely.
• Scope-limited change touching only apps/fabric/.dockerignore and apps/fabric/.gitignore and preserves current .fabric ignores and existing behavior.

Testing

• Ran git -C apps/fabric check-ignore .fabric/config.json .paperclip/config.json .fabric-local/token .paperclip-local/token and verified legacy Paperclip paths are now ignored.
• Ran git diff --check with no new ignore-related warnings.
• Ran npm run typecheck in apps/fabric which completed successfully.
• Attempted npm run lint but the workspace has no lint script.
• Ran npm test in apps/fabric; the test run surfaced unrelated existing failures (embedded Postgres root-user limitation and several failing unit tests) and was interrupted, so full test-suite success was not verified in this environment.

---

Codex Task

[DeployFaith]

Superseded by #101, merged to main as 4133675 after all required GitHub checks passed.