[Feature Request]: Have specific row listeners for putRowTo() and getRowTo()

### What would you like to happen?

Some transforms produce output of varying nature. For example the Workflow and Pipeline Executor transforms can generate various types of output like the result, result rows, output rows, result files and so on.
If we attach a row listener to this transform we'll get rows with varying layout in the listeners without a way of keeping them apart by target transform.
We have the same problem for info rows entering a transform with getRowFrom().

Suggested for Hop 3.x

### Issue Priority

Priority: 3

### Issue Component

Component: Api

Start by tracing the existing putRowTo() and getRowTo() APIs and how row listeners are registered. Determine how listeners could distinguish target transforms and how info rows entering through getRowFrom() should be separated; done means the API supports specific listeners without mixing varying row layouts.

Written by the indexing model from the issue text.