RFPL-2752: Metamer: add profile for richfaces binaries replace

This profile provide ability to test backward compatibility. On current sources (ftests version) should be replaced richfaces binaries by version provided by "metamerapp.tested.version" variable before metamer.war is deployed into target platform and ftests performed.
RFPL-2752: Metamer: fix metamer deploy problem with bacward compatibility profile

Since richfaces 4.3 requires run JBoss AS with standalone.xml instead of standalone-full.xml as set in arquillian.xml in 4.2.x branch, it is required update arquillian.xml within backward-compatibility-testing profile to met this condition
RFPL-2752:Metamer: add backward compatibility profile for WFK

Since there are some problems with WFK dependencies (at least metamer.war) it would be easier run tests without care about dep. using maven, and just use ones from somewhere on filesystem prepared before run tests.
New maven property "metamer.wfk.dependencies.dir" introduced, which has to point to dir where metamer.war and richfaces jars are placed. It requires no jars containing here if they cannot be copied into metamer's WEB-INF/lib folder.
RF-11382: Metamer: add issue simulation
Selenium updated to version 2.31
Merge remote-tracking branch 'origin/4.2.x' into wfk21