[bojemoi] feat: multi-stage Dockerfiles, DVAR IoT target, bm12/uzi ARM enrichment

Commit `a79479d`

Dockerfiles:

Convert 8 Dockerfiles to multi-stage / virtual build-deps pattern:
- oblast/Dockerfile.zaproxy: remove make/ant/automake/autoconf/gcc from final stage, openjdk-jdk → jre
- telegram-bot, discovery: proper builder/runtime stages, gcc+libpq-dev removed from runtime
- tsushima: dedicated masscan-builder stage + –virtual .ruby-build-deps
- borodino/Dockerfile.borodino, berezina/Dockerfile.berezina: –virtual .build-deps removed after bundle install
- narva/Dockerfile.narva, borodino/Dockerfile.berezina: remove unused build tools (no bundle install)
Compile Python sources in: mcp-server, discovery, sentinel/collector, koursk-2
cccp.sh: docker buildx build –push (direct registry), ensure_registry() boot stack check

DVAR IoT:

dvar/: Dockerfile.dvar (QEMU ARM emulation, cross-compiled vuln HTTP server), entrypoint, vuln_httpd.c
stack/56-service-dvar.yml: pentest + iot_network networks, worker placement
scripts/metasploitable2_exploit.py: Metasploitable2 exploit helper

Borodino bm12/uzi:

thearm_bm12: arch detection (_ARCH_PATTERNS, _IOT_KEYWORDS), IoT/ARM banner parsing, stores arch in hosts.arch
thearm_uzi: ARM/MIPS payload selection, IoT OS path, host_arch from DB, generic IoT support
stack/40-service-borodino.yml: bm12_v3 scan_status target, updated service config

Co-Authored-By: Claude Sonnet 4.6 noreply@anthropic.com