Add Odoo JSON-2 connector slice

[harrisonoconnorhover]

Summary

• add a read-only Odoo 19+ JSON-2 res.partner extraction engine
• use bearer API-key authentication, optional database routing, bounded offset pages, and an inclusive write_date watermark
• normalize Odoo's false sentinel for nullable non-Boolean fields while preserving declared schema validation
• add the connector template, customer/partner staging model, operator documentation, CLI routing, and focused tests

Validation

• uv run ruff check .
• uv run ruff format --check .
• uv run mypy src tests
• uv run pytest — 672 passed after rebasing onto NetSuite-enabled main
• earlier live acceptance against ephemeral official Odoo Community and PostgreSQL containers: bounded pages, bearer auth, database routing, null normalization, and watermark replay all passed; containers were removed afterward

Boundaries

The first slice is read-only res.partner. It does not add a retained-project pipeline, deployment, version bump, package publication, or support claim for large concurrently mutating Odoo tables. Deprecated XML-RPC/JSON-RPC APIs are intentionally out of scope.