Remove previous boilerplate code

* This will be to give a clear "add new framework" example.
Add Eclipse Android Developer Tools support

* Install Eclipse ADT on its own path with its requirements.
* Select correctly the 32 bits or 64 bits versions zip download.
* Same license selection than Android Studio.
* Not default of the android framework: android studio beta is the default.
* Copy an icon (48x48) for its desktop file in the user directory, found in
  the eclipse package.
* Can be installed with: $ udtc android eclipse-adt.
Adapt number of android frameworks in tests

* Small tests expected one android framework, we have 2 now.
Add large tests for Eclipse ADT

* Copied mostly from the Android Studio large tests, however:
- we removed the tests for the default framework of the android category
  (it's not),
- we modify the way we detect the java process and ensure we download the right
  32 bits or 64 bits version (as this will run on both configs in the QA DC)
- there are some subtilities in the return code while killing the parent java
  process
Add assets for medium Eclipse ADT tests

* Create a 32 and 64 bits zip + the index page referencing them.
* The difference between the 2 assets is that they are calling the sub java
  process with -arch <arch>
Add medium tests for Eclipse ADT

* Add md5sum for the fake assets.
* Inherit from large Eclipse ADT tests, running in a container.
* As for Android Studio, add a wrong md5sum test that we server inside the
  container.
* Modify slightely large tests as the assets really returns a 143 error
Ignore rotating logs as well.
Rename desktop_file_name to desktop_filename
Add support for optional icon_filename arg
Merge branch 'master' into eclipse-adt
Don't duplicate desktop_filename assignement
Merge branch 'master' into eclipse-adt
Support latest BaseInstaller API to avoid dup.

* Avoid duplication of desktop_file_name assignement and rename to
  desktop_filename
* Comply in adding new icon_filename assignement to enable automatic removal
  of the icon on uninstall.
Handle if reinstall in other directory than origin

* If we do reinstall in another directory than the original one, we have to
  potentially have to clean 2 directories: the original one, and the new
  one up for installation if it's not empty. Fix the logic about this and clean
  up the code to be more flexable and cleaning both if needed (reasking if the
  new path up to installation isn't empty as well). Set the install_path way
  later for that reason.
* Mark the config file up only at the end of a successful installation as we
  delete the original installation at the very end of the installation process.
  (this enables to keep a trace of where it was installed to be able to remove
  it at the second reinstall request if the first one failed).
Remove previous boilerplate code

* This will be to give a clear "add new framework" example.
Move paths to remove to a set
Fix a test as we need to set the install_path

* The requested install_path needs to be set as install_path before marking
  it into the configuration.
setup() doesn't need install_path argument anymore

* update the baseinstaller to not add that argument
* update all the tests as well
Add a remove_from_config utility

* This enables to remove from the udtc config file any registered framework
* Add corresponding tests
Add removal feature to frameworks

* All frameworks have now a --remove option enabling them to uninstall
  their desktop file, icon, projected content and udtc config.
* Add corresponding tests.