Mechanism to prevent or detect potential user configuration error.

There have been many instances where folks have had problems with custom end-to-end mode configurations. In most of these cases, this is due to having a source that depends on having a corresponding sink down stream. There are several of these pairs in the system. (ackInject/ackChecker, batch/unbatch, gzip/gunzip, benchmarkInject/benchmarkReport),

It really seems that we should have a "type-checking" like mechanism that can present users the potential problems that could occur in their data flow.

This "epic" is a place to continue this design discussion.