Provide working SWTBot Tests for the example project about spray HOT 6 CLOSED

If the first SWT Bot tests are available, I will enable them in the build.

Found useful post here: 
http://dev.eclipse.org/mhonarc/lists/tycho-user/msg00466.html

Execution of the SWT Bot tests are now included in the build.

For the CI Build they are disabled (by activating profile "skip-ui-tests".

Currently the example one example SWTBot Test is very fragile. It works only on 
certain machines, sometimes if cannot found actual visible elements in the 
dialog and thus abort and so on.

Some problems may fix with more use of async access blocks and sleeps. But if 
this is enough, one should consider evaluating one of these tools instead: 
 * http://code.google.com/intl/de-DE/javadevtools/wintester/html/index.html
 * http://www.eclipse.org/jubula/

The testing of UI is still very important as some problems only occur in a 
running Eclipse (ok, some of these issues may be covered by Simple JUnit 
plug-in tests). The UI test tool to choose, should produce predictable results 
and should be able to test GEF based stuff.

There is a test case for the default use of the Spray wizard to create a new 
Spray project, then inserting the custom Spray Xtext definition and then 
running the generator:

http://code.google.com/a/eclipselabs.org/p/spray/source/browse/tests/org.eclipse
labs.spray.examples.one.tests/src/org/eclipselabs/spray/examples/one/tests/Wizar
dTest.java

There is still lot to do, e.g. currently there is no validation of the results 
of the UI test, the special cases are not covered yet (different configurations 
in the wizard, although the test infrastructure allows customization easily).

Another things, that a Maven Tycho build is currently not able to set up a 
PDE/OSGi enabled Eclipse test instance, so you cannot run a UI test that 
creates plug-in projects that needs dependency resolving or even more to use 
these just created plug-in projects to start a further Eclipse instance, e.g. 
to check if your able to create Graphiti diagram from the generated projects.

So these test steps have to be split up:
1. Test the generation and use of the Spray diagram project
2. Test the usability of the just before generated and Spray diagram project to 
create a Graphiti diagram (this would be a further UI Test process using the 
generated Spray diagram project as plug-in dependency - so this project must be 
available from somewhere, e.g. from a tmp directory)

As this task is to big to track, it will splitted in smaller issues. Thus this 
issue will be marked as fixed in context of providing a reusable test 
infrastructure.