Add input fields that allow the user to assign values to various parameters

[mahendrark]

Fix #114

Changes proposed in this pull request:

• Your_changes

The following steps were realized, as well (if applies):

• Apply black (black . --exclude docs/)
• Update the CHANGELOG.md

The following optional steps were realized:

• Use in-line comments to explain your code
• Write docstrings to your code
• For new functionalities: explain in readthedocs
• Write test(s) for your new patch of code

_{For more information on how to contribute check the [CONTRIBUTING.md](https://github.com/rl
-institut/open_plan/blob/dev/CONTRIBUTING.md).}

[mahendrark]

Initial workflow proposal:

1. Create a dictionary in macro in create_project.html with 5 different parameters for project parameters.
2. Loop through this dictionary and create Foundation form elements with input data fields. Docs here and here
3. The input fields must have the attributes described in the docs here

After successful initial workflow execution:

1. Add option (above the input fields) to load a CSV file which is then converted to a Pandas DF and from which the parameters and their values are determined. This can be saved into a dictionary (same as the one hardcoded above).
2. If user decide to load the parameters from disk system, then step 1 is executed and the values of the parameters must be populated automatically in the input fields, from the dictionary obtained in step 1.

@Bachibouzouk comments?

[mahendrark]

Tasks to do:

1. Fix the layout of the input fields
2. Auto fill the fields with values from csv, if the user loads in a csv using the button above the input fields (example here)
3. Add styling to the view-component

[mahendrark]

@Bachibouzouk

I did some preliminary work, but there are some problems.
Like for e.g.: The default values and type of data for each field (numerical or textual) does not work. I think the problem is how I am trying to access the value from dictionaries. Can you please take a look?

[Bachibouzouk]

why do you loop here, you can assess the value directly with param_details["docs_link"]

[Bachibouzouk]

I think the structure should be a list of dicts (you can move the name inside with the key name or label for example

[Bachibouzouk]

We should probably create models and use ModelForm to render the inputs from the model instances. The column value will pose problem in a database if the values are from different types (text, number, array), we could avoid that problem by creating one Modelclass per parameter type, that way the types in the column values will not be mixed