feat(Forms) : rendering lib based on json-schema-form-core

[jmfrancois]

What is the problem this PR is trying to solve?
The actual form implementation is based on mozilla's react-jsonschema-form lib which is too restrictive and miss a lot of features.

The biggest point is that it ties jsonSchema (which should represent the model), with the uiSchema format (which should represent the form, what widget, where it should appear).

For example, if we want a tab widget to manage a fieldset by tab, the jsonSchema (so the model) will be something like that :

{
    tab1: {
        lastname: '',
        firstname: '',
    },
    tab2: {
        address: '',
        city: '',
    }
}

If we want flat data but displayed with tabs, that is not possible. This introduce issues with daikkon forms.

What is the chosen solution to this problem?

Reimplement a lib based json-schema-form-core for jsonSchema/uiSchema parsing.

You can start by reading the README

Please check if the PR fulfills these requirements

• The PR commit message follows our guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)
• Related design / discussions / pages (not in jira), if any, are all linked or available in the PR

[ ] This PR introduces a breaking change

[jmfrancois]

waiting for json-schema-form/json-schema-form-core#4 to continue

[build-travis-ci]

Demo is available here

[build-travis-ci]

Demo is available here

[build-travis-ci]

Demo is available here

[build-travis-ci]

Demo is available here

[build-travis-ci]

Demo is available here