Configuration Validation

[fm-tibco]

Current behavior:
No explicit configuration validation via json schema

Expected behavior:

Generate json schema for flogo.json configuration and all resources. A project should have the ability to enable/disable configuration validation. If configuration is disabled, schema validation related imports should be excluded. Engine shouldn't include the validation code if it is not being used.

What is the motivation / use case for changing the behavior?

Additional information you deem important (e.g. I need this tomorrow):

We should enable configuration schema validation code loading by convention

• if enabled add import for flogo.json validation

• if enabled add import for each action (for their resources)
  (ex. /config/validation)