Create a strict vs. lax type comparison option for Pipeline connection validation

[sjrl]

Create a strict vs. lax type comparison option – Allow users to choose whether type checking should be strict (e.g., Optional[str] → str fails) or more permissive (e.g., Optional[str] → str passes).

[sjrl]

After offline discussion with @wochinge we believe it makes more sense to introduce a type_validation parameter which can be True or False to control whether type compatibility checks are made. This allows advanced users to turn off type validation for pipeline connections if they want to and allow for things like sending Optional[str] to str