Feature conflict with software repositoriy and local shared software

[hohwille]

We have two advanced features:

1. Remote software repository - see Ability to configure software downloads via settings config #98
2. Shared local software cache - see ability to configure central software installation directory #152

However, if these two features are combined undesired things can happen. So to be precise:
The implementation of 2. needs to separate software per repository.
Unlike a maven repository we can not be sure that a combination of tool, version, and OS will lead to the same binary no matter what repository is configured for 1. The idea of 1. is actually for projects to provide a customized version of a tool (e.g. use Java from a different vendor, use Eclipse with a preinstalled set of plugins, etc.).
The feature 2. only makes sense if you mave multiple installations of devon-ide in parallel. Now if some of these installations use different configurations for 1. the devon-ide will accidentally use the software of the one also for the other even though they should be different.

To fix the issue the structure of the shared software folder for 2. needs to be extended to:

${DEVON_SOFTWARE_PATH}/${software_repo}/${software_name}/${software_version}

Where ${software_repo} is one of:

• default if 1. is not used
• some unique identifier for 2. - IMHO the hostname should already be sufficient. To be more reliable a hash of the entire URL could be appended.

[hohwille]

Fixed with PR #201