Remove obsolete experimental modules

As previously discussed on the dev@ list, these experimental
modules are no longer needed and better served with
alternatives, or with a refocused effort.

Conflicts:
	pom.xml
	wicket-experimental/wicket-bootstrap/pom.xml
	wicket-experimental/wicket-bootstrap/src/main/java/org/apache/wicket/bootstrap/Bootstrap.java
	wicket-experimental/wicket-examples-parent/pom.xml
	wicket-experimental/wicket-examples-parent/wicket-examples-jar/pom.xml
	wicket-experimental/wicket-examples-parent/wicket-examples-jar/src/main/java/org/apache/wicket/examples/base/Examples.java
	wicket-experimental/wicket-examples-parent/wicket-examples-jar/src/main/java/org/apache/wicket/examples/base/prettify/Prettify.java
	wicket-experimental/wicket-examples-parent/wicket-examples-jar/src/test/java/org/apache/wicket/examples/base/markdown/MarkdownTest.java
	wicket-experimental/wicket-examples-parent/wicket-examples-war/pom.xml
Make experimental modules releasable in 6.x and 7.x

Having the experimental modules in one and the same groupid makes it
impossible to maintain the experimental modules in both 6.x and 7.x
branches--they will be unreleasable due to conflicting version numbers
and users will be confused which release is compatible with which
version of Wicket.

By moving the experimental modules into their own wicket version specific
group id, we can release both experimental modules with wicket releases
for the corresponding major branches.

Conflicts:
	pom.xml
	testing/wicket-common-tests/pom.xml