Introduce time.Time as a first class citizen in data.Type

[balamg]

I'm submitting a ... (check one with "x")

[] bug report => search github for a similar issue or PR before submitting
[x] enhancement request
[] feature request
[] support request
[] general question

Current behavior (how does the issue manifest):

Expected behavior:

Minimal steps to reproduce the problem (not required if feature enhancement):

What is the motivation / use case for changing the behavior?
It would be great to have time.Time as a first class citizen in data.Type and related type conversions/coercion
Please tell us about your environment (Operating system, docker version, browser & verison if webui, etc):

Flogo version (CLI & contrib/lib. If unknown, leave empty or state unknown): 0.X.X

Additional information you deem important (e.g. issue happens only occasionally):