Support more than 1 task type for stage outputs

Is your feature request related to a problem? Please describe.
Currently many stages typically work with a single type of task as input/output for eg: DocumentBatch or VideoTask.
Even if a stage accepts different task types often they may have the same input/output requirements ["data"]["text"].
However with more cases of stages being applicable cross modality and cross task there might be cases where the input and output spec vary depending on the task type.

For eg: MinHashStage can be extended to operate on DocumentBatch in addition to FilegroupTask. However the input requirements for fgtask is (["data"], []) however for DocumentBatch it would be (["Data"], ["text","id"]). Which breaks validate_inputs in many cases or forces the stages to include the least amount of validation requirements to allow multiple types to work.

Describe the solution you'd like
One thing to decide here is it the output type depends on the input type or maybe depends on other factors instead

Describe alternatives you've considered
Alternative is for each stage with this requirement to override the validate_input/validate_output stage to handle the custom branching logic.

Additional context
Add any other context or screenshots about the feature request here.

Start by tracing stage input and output validation, especially validate_inputs and the validate_input/validate_output overrides mentioned in the issue. Use MinHashStage and its FilegroupTask and DocumentBatch requirements as the concrete cases. The design must decide whether output requirements depend on input task type or other factors, then support the differing specifications without weakening validation.