Disable modal dialogs at eclipse startup (usage etc.)

These properties should disable subclipse, jbt usage reporting
and atlassian dialogs at startup
Fixed Red Deer API change in JBoss server requirements

Method isEnabled was moved from WidgetLookup to handler.
Using WithTextMatcher and DefaultHyperLink.
Refactored final fields in JBoss server requirements
Renamed package with advanced examples in JBoss server requirements
Fix WildFly server label - remove experimental str
OpenShift: implemented github app test case
Fixed omitted Label and minor timeouts fixes
Updated javadoc and fixed changes in Web Services

Changes were made in validation of applications (there are errors instead
of warnings).
Update parent pom to version 4.2.0.Beta1-SNAPSHOT
Changed DefaultCombo to LabeledCombo
AS tests: Changed retrieving of server module + using Labeled combo instead of DefaultCombo.
Removed JBTTestCase from AS tests + added properties to launchers + removed Section.
added IDELabel class containing base label constants
removed archvies dependency on swtbot
AS: Implemented unsupported editor features.
changed maven dependency from tools.maven.profiles to eclipse.m2e.profiles
Added CXF 2.x Web Service Client test

CXF 2.x is Web Service Runtime so there is a new class WebServiceRuntime
which is used to distinguist between CXF 2.x and JBoss WS runtime.
It's downloaded via maven download plugin and path to it is stored into
properties file ws.properties.

Tests for WsClient was extracted to WsClientTestTemplate which
covers testing. It's a super class for CxfWsClientTest and
WsClientTest, which specify the WebServiceRuntime.

Adding choice of Web Service Runtime, which is used to create dynamic web
project, brings problems with different dialogs layout and also need of having
more informations (like name of ear project).

There is also huge refactoring. This was also opportunity to reimplement
methods and implement new ones using Red Deer API.
Added Wildfly8.0.0.Final to mavenized runtime tests
Fixed JBoss Server requirements with processing a New Adapter Page

The workflow of creating server via New Server dialog has been changed.
There is a new wizard page, which brings options to set up profile and
to create remote runtime without a server.

Therefore, JBoss Server requirements had to be updated.