TaskScheduler NO_OP type does not accept an injected value

TaskSchedulers NO_OP feature is not well implemented IMO.
While wiring a NO_OP scheduler works with no issue, if you inject a value into that wire, you will get an exception.
That forces client classes to perform a check to verify if the component is a no-op or not before injecting a value, completely defeating the benefit of having types of schedulers.

We need to determine the semantic meaning of injecting a value into a wired no-op scheduler; does it simply swallow the input without producing an output on the connected wire? Or does it produce a default value?

_Originally posted by @mxtartaglia-sl in https://github.com/hiero-ledger/hiero-consensus-node/pull/20758#discussion_r2291086288_

Start by locating the TaskSchedulers.NO_OP implementation and read the originating pull-request discussion linked in the issue. The payload names no file or test; the work is complete once the injected-value semantics are decided, documented in the implementation contract, and verified for the chosen behavior.

Written by the indexing model from the issue text.