Introduced JSoup implementation and increased to 8 threads

JSoup has been introduced to parse and process the XML.
This is because Selenium  goes back to the server to verify HTML has not changed (even when querying a retrieved table cell).
The additional server calls use a lot of extra TCP connections.
The overhead of using JSoup is more than offset by reduced server trips, reduced TCP connections, and ability to use more threads (Number of threads previously limited by windows TCP connection limit).
Optimal number of threads appears to be between 4-8 (only limited testing carried out).
Runtime appears to be cut from 20 mins to 15 mins as a result of this change.

Fix a bug in TestPersistence
Renamed WebDriverFactory (typo)
Pom.xml - added dependency on JSoup
Runner.java - increased Threads from 3 to 8.
New classes:
IPlayerManager
PlayerManagerJSoup
PageProcessorJSoup

IPlayerManager now passed into the PageProcessorJSoup Constructor
PageProcessor retrofitted to use IPlayerManager - interface is unchanged but usage being replaced by PageProcessorJSoup

Known issues:
Note there is a typo in project path - /projets/
Unit tests could now be implemented testing against both PlayerManager classes using live HTML or the JSoup version using static HTML.