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