Resolves: #2147

Purpose
This PR implements dynamic WoT (Web of Things) validation configuration endpoints for Ditto, enabling runtime CRUD operations for validation settings via a new DevOps REST API. This allows for flexible, real-time updates to validation rules, especially useful during model migrations or deployment transitions, without requiring service restarts.

Key Features

1. New DevOps REST Endpoints
   All endpoints are under /devops/wot/config:
   GET /devops/wot/config
   List all dynamic validation configs (by scope).
   GET /devops/wot/config/{scopeId}
   Retrieve a specific dynamic validation config section.
   PUT /devops/wot/config/{scopeId}
   Create or replace a dynamic validation config section.
   PATCH /devops/wot/config/{scopeId}
   Partially update a dynamic validation config section.
   DELETE /devops/wot/config/{scopeId}
   Delete a dynamic validation config section.
   GET /devops/wot/config/merged
   Retrieve the merged (static + dynamic) effective validation config.
2. Distributed Persistence and Synchronization
   MongoDB is used for persistent storage of dynamic validation configs.
   Pekko Distributed Data (DData) is used to distribute dynamic config state across all Ditto instances in the cluster.
   When a config is updated via the API:
   The change is persisted to MongoDB.
   DData is updated, which automatically synchronizes the new state across all nodes.
   All Ditto instances immediately see the latest config, ensuring strong consistency and real-time updates.
3. Startup and Merge Logic
   On startup, each instance loads the static config from things.conf.
   Dynamic configs are loaded from MongoDB and distributed via DData.
   The effective validation config is computed by merging static and dynamic configs, with dynamic overrides taking precedence for their scopes.

Benefits
Real-time, cluster-wide updates: Instantly change validation rules across all Ditto instances, with no restarts required.
Safe migrations: Temporarily relax or tighten validation for specific models or scopes.
Consistent distributed state: DData ensures all nodes have the latest config, with no manual cache management.
Separation of static and dynamic: Static config remains as a fallback; dynamic config is layered on top.