TransformingOutputWire.forward() skips remaining destinations and cleanup on null transform result

Problem
In TransformingOutputWire.forward() (platform-sdk/consensus-wiring-framework/src/main/java/org/hiero/consensus/wiring/framework/wires/output/internal/TransformingOutputWire.java), when transform.apply(data) returns null for one destination, the method does return instead of skipping to the next destination. This has two effects:

1. Remaining destinations in forwardingDestinations are never visited for this data item, even though a stateful transform may return non-null for them later — inconsistent fan-out.
2. inputCleanup.accept(data) (which runs after the loop) is skipped entirely, leaking whatever resource the input holds (ref counts, off-heap buffers, etc.) on every null-transform occurrence.

Separately, the catch (Exception e) branch swallows failures from transform.apply/destination.accept but never invokes outputCleanup on a transformed value that was produced but never delivered — a related leak on the error path.

Proposed fix

• Replace the null-check return with continue.
• Wrap the loop so inputCleanup.accept(data) runs exactly once per item on every exit path (success, null-transform, exception) — e.g. try/finally.
• On exception in destination.accept(transformed), invoke outputCleanup.accept(transformed) for the undelivered value, consistent with the OFFER-reject path.
• Unit tests: null transform on a non-last destination still reaches later destinations; inputCleanup fires exactly once regardless of null/exception; outputCleanup fires when a destination throws after transform produced a value.

Reference: originally flagged as VLN-612 (hedera-security-issues#700) — confirmed not a security issue, but a real resource-leak / inconsistent-fan-out bug needing a fix and tests.