Unlink Init-class from a file (includes: Reducing multiton-behaviour)

It feels unnecessary , that the `Init`-class is always bound to a specific file path, because nothing made use of the `getConfigPath()` outside of `Init`. Also the multiton-behaviour seems unnecessary. 

This PR allows to instanciate the `Init`-class directly with an `array` of config parameters. `getConfigPath()` and `setConfigPath()` is gone. This should make it easier to integrate IDS into applications, because they can use other connfiguration file formats, the data from an application-wide configuration, or no config-file at all (means "hardcoded" for whatever reasons).

I would have removed the multiton-behaviour completely, but because of unknown reasons many tests start to fail, when `Init::init()` returns new objets, instead of cached ones.