Rule Idea: Pipeline Type Checking against Output

This is just a spitball idea to contribute feedback if it is maybe feasible, I might consider attempting a PR

Problem

Often when writing a pipeline you may pipe an incompatible type, and you won't find out until runtime.

Proposed solution

If the output type of a function can be explicitly determined by:

1. Use the .OUTPUT comment based help section to define the output type of a function
2. Take all explicit return keywords that explicitly cast to a type e.g. return [MyType]@{} or can be simply derived from a typed variable e.g. $f = [MyType]::new();return $f

And the function being called either to or from meets the following criteria:

1. Has strictly typed non-primitive parameter or ValueFromPipeline

Then we should be able to safely issue a warning or error stating something like "MyFunction expected [MyType] but is receiving [WrongType] via the pipeline" as a static analysis.

#Issues

1. Easily castable types like string we have to exclude, they will basically always match
2. Probably should support/detect explicit casts or interfaces

Prior Art

How JSDoc can be used to test for type safety in normally-untyped javascript.

Empieza revisando las fuentes propuestas de tipos de salida, las comprobaciones de los parámetros de la pipeline, las excepciones de casting y los antecedentes de JSDoc descritos en el issue. Define el punto de entrada y el alcance del analizador antes de la implementación; se considera completado cuando un enfoque decidido puede detectar tipos incompatibles en la pipeline, excluyendo los valores que se pueden convertir de forma segura y gestionando los casts explícitos o las interfaces.