Update build container to use latest development image

Update the ESP32 build job in CI to use the `ghcr.io/jethome-iot/litepb-dev:latest` container image and adjust replit.md to reflect this change.

Replit-Commit-Author: Agent
Replit-Commit-Session-Id: 79c60e56-af99-4011-a509-f8e82de07405
Replit-Commit-Checkpoint-Type: full_checkpoint

Author: Hacker-CB

.github/workflows/ci.yml

@@ -43,7 +43,7 @@ jobs:
     name: ESP32 Build
     runs-on: ubuntu-24.04
     container:
-      image: ghcr.io/jethome-iot/jethome-dev-platformio:latest
+      image: ghcr.io/jethome-iot/litepb-dev:latest
       credentials:
         username: ${{ github.actor }}
         password: ${{ secrets.GITHUB_TOKEN }}

replit.md

@@ -27,7 +27,7 @@ Communication style: Simple, everyday language
 - **Header Guards**: All C++ headers (manual and generated) use `#pragma once` for simplicity and modern compiler compatibility.
 - **Containerized Development**: Utilizes a Docker environment (`ghcr.io/jethome-iot/litepb-dev:latest`) for consistent builds and CI/CD pipelines, including Python, build tools, code quality tools, and the `protoc` compiler.
 - **Testing**: Comprehensive test suites including 168 PlatformIO unit tests and 18 interoperability tests (186 total). Interop tests verify wire format compatibility across all Protocol Buffer features: basic/signed/fixed scalar types, repeated fields (packed/unpacked), maps (various key-value types), nested messages, oneof fields, enums (top-level/nested), proto3 optional fields, empty messages, large field numbers, and unknown fields preservation. The interop tests use a `RoundTripConfig` template struct with lambda-based test builders and verifiers, eliminating ~700 lines of boilerplate code. Each test provides lambdas for building/verifying LitePB and protoc messages, with optional binary equivalence checking and post-round-trip hooks. PlatformIO tests cover all core functionality including ProtoReader/ProtoWriter primitives, streams (BufferOutputStream/InputStream, FixedOutputStream/InputStream), unknown fields, and complete message serialization. Code coverage reports are generated.
-- **CI/CD**: GitHub Actions workflows (`ci.yml`, `build-docker.yml`) manage continuous integration and deployment, performing format checks, running tests, building examples, and verifying ESP32 build compatibility. The ESP32 build job uses a specialized PlatformIO container (`ghcr.io/jethome-iot/jethome-dev-platformio:latest`) and ensures both `esp32_core` and `esp32_serialization` environments compile correctly without requiring physical hardware.
+- **CI/CD**: GitHub Actions workflows (`ci.yml`, `build-docker.yml`) manage continuous integration and deployment, performing format checks, running tests, building examples, and verifying ESP32 build compatibility. All CI jobs use the same development container (`ghcr.io/jethome-iot/litepb-dev:latest`) for consistency. The ESP32 build job ensures both `esp32_core` and `esp32_serialization` environments compile correctly without requiring physical hardware.
 
 ## External Dependencies
 - **PlatformIO**: Build automation, dependency management, and testing frameworks for embedded projects.