duckling parser is trying to be invoked right out of the box

[greed2411]

adapting the code base from a template like repository to core-slu service has caused backward compatibility for:

earlier because of template config it was not creating duckling related section in the prediction.py but since core-slu coming in. it has them by default and tries to load/invoke Duckling.

therefore adapt these changes in:

• config/config.yaml.jinja (to include it as a section in it and set it's usage to false)
• make relevant changes to Config (config.py) to consider that usage with new object variables.
• adapt the controller/predict.py on whether to include duckling parser in preprocessors or not as per the Config variables mentioned above (derived from config.yaml)