Add format and length validation to ingest ipAddress to mitigate SSRF

[birme]

Summary

• Add a strict IPv4/IPv6 pattern (plus the existing maxLength: 128) to the ipAddress field of the NewIngest TypeBox model in src/models.ts, so malformed values are rejected at the schema boundary with a 400.
• This closes an SSRF / request-injection gap: IngestManager.fetchDeviceData() will use ipAddress for outbound device communication, and the value was previously a free-form Type.String() accepting URL schemes, paths, credentials, whitespace and CRLF.
• Use pattern rather than format because ajv-formats is not registered in this project, so format keywords are documentation-only and are not enforced; pattern is a core JSON Schema keyword and is always applied.
• Add a SECURITY note near the fetchDeviceData TODO in src/ingest_manager.ts reminding that any real implementation must additionally reject private/reserved/loopback/link-local ranges before making outbound requests.
• Extend src/api_validation.test.ts with a valid-IPv6 acceptance case and a parametrised set of malformed/injection inputs (scheme, path, port, hostname, out-of-range octets, trailing space, CRLF) that must be rejected with 400.

Test plan

• Tests pass (npm test — 358 passed, 18 suites)
• TypeScript compiles (npm run typecheck)
• Lint clean (npm run lint — 0 errors; pre-existing any warnings only)
• Prettier clean (npx prettier --check on touched files)
• Valid IPv4 (127.0.0.1) and IPv6 (2001:db8::1) reach the handler (501), malformed inputs are rejected (400)

Closes #250

🤖 Generated with Claude Code

[birme]

Code Review — Verdict: LGTM

Reviewed by a separate code-reviewer invocation (not the implementer). Summary: adds a correct, ReDoS-safe IPv4/IPv6 pattern to NewIngest.ipAddress, closing the schema-boundary gap that let arbitrary strings (URLs, paths, CRLF) reach the SSRF-prone fetchDeviceData path; includes a SECURITY note and thorough regression tests. No Blocking or Warning items. CI green (lint, pretty, ts, unittests).

This PR is self-authored by the automation account, so GitHub blocks a state-bearing self-approval; recording the verdict as this marker and merging via admin per the daily-backlog-pr skill.