fix(vdr): reject VDR operations containing unknown protobuf fields (#890)
VDR storage operations (CreateStorageEntry, UpdateStorageEntry, DeactivateStorageEntry) that carry unknown protobuf fields are now rejected with a ValidationError during parsing. Unknown fields indicate a schema mismatch or a malformed/tampered message. Accepting them silently could cause two nodes running different protocol versions to diverge on stored VDR state. SSI operations (CreateDID, UpdateDID, DeactivateDID) are intentionally left lenient so future protocol extensions remain forward-compatible. The guard is implemented as a private helper `ensureNoVdrUnknownFields(outer, inner)` that checks both the outer AtalaOperation wrapper and the inner storage operation message using ScalaPB's `unknownFields: UnknownFieldSet` field present on every generated message. Four new tests cover: - parseCreate rejects unknown fields on the inner message - parseCreate rejects unknown fields on the outer AtalaOperation wrapper - parseUpdate rejects unknown fields on the inner message - parseDeactivate rejects unknown fields on the inner message Signed-off-by: Yurii Shynbuiev <[email protected]>