Consider bridging lambdas the same way we bridge `Flow`

[JakeWharton]

Today you have to use a named type which extends from ZiplineService, but we could automatically bridge the lambda itself and now only the lambda parameters and return type would be constrained by the need to be serializable (or ZiplineServices).

---

Can lambda Function be implemented internal zipline in a way similar to Flow?

Originally posted by @qhyuan1992 in #1494 (reply in thread)