Only by copying the produced product and setting the test configuration
to "p2Installed", the efxclipse osgi extensions are activated on
startup. This is required to get JavaFX up and running. Due to a recent
code modification, JFX code is already loaded during startup such that
JavaFX is now also need.
The absence of JavaFX was not noticed before since no JFX classes were
loaded by kernel services, nor did any test require them.
In addition to fixing the initial bug, we are also testing the produced
build now and not only a subset.

Signed-off-by: Alexander Diewald <diewald@fortiss.org>