Add cs.money worker stack with per-worker IPRoyal residential proxy

Brings up the pull-model scraper: the .NET C2 hands skin+wear jobs to Python nodriver workers that scrape cs.money and post results back, plus the supporting Core/EFCore data model, migrations, and docker-compose orchestration.

IPRoyal proxying lets workers scale horizontally with a distinct residential exit IP each: every worker process mints its own sticky session at startup, and an in-process forwarding proxy injects the gateway auth so Chromium talks only to an auth-free localhost endpoint (zero CDP). On a Cloudflare challenge a worker rotates to a fresh session/IP and re-warms. Verified end-to-end against live IPRoyal: distinct US residential exits per worker and IP rotation on demand.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

.dockerignore

@@ -0,0 +1,22 @@
+# Keep build contexts small/clean (both images use the repo root as context).
+**/bin/
+**/obj/
+**/.vs/
+.git/
+.gitignore
+*.user
+
+# Python worker local artifacts
+worker/.venv/
+worker/__pycache__/
+worker/captures/
+
+# Discovery dumps
+csmoney-probe/
+csmoney-captures/
+
+# Docs/markdown aren't needed in images
+**/*.md
+
+# Secrets: compose reads .env for variable substitution; never bake it into an image
+.env