Division changes and PublicWhip1 accessible

• Changes to how divisions are access to allow for editing (separating out the raw Hansard motion data from the vote summary and the edited motion text)
• Allow PublicWhip1 to be accessible on Docker (port 81) for side-by-side testing
• Add lots of unit tests (up to 34.56% of lines) and fix a few related bugs.

Move to Doctrine coding standard

Merge pull request #5 from publicwhip/rb-doctrineCodingStandards

Change to doctrine based coding standards and more strict QA checks.

Divisions fix.

Added code from originalPublicWhipCode and associated data extractors (in v1migrationUtils) to allow for comparisons of wiki stored division data.

Added unit tests to check those extractions. Fix problem with code coverage export.

More coding style improvements and fixes.

Standardise on the spelling/format of PublicWhip.

Improved coding style and fixes

Merge pull request #3 from publicwhip/rb-0.4.1-code-stylings

Rb 0.4.1 code stylings

Divisions are now properly read

Division motion text is stored in a custom 'wiki' format which needs to be parsed.
Removed the hydrator as it wasn't useful (and in tests, was shown to be slower than the new solution).
Removed the qaTools folder which, whilst has made the root directory/folder 'messier', it has simplified configuration for people.

Add missing data files

Added continuous integration settings, missing database tables (for policies), added planned milestones, fix indentation in composer.json.

Prepare for upload to Github

The system should present a basic styled POC (proof-of-concept) website with
information about the project, there should be an appropriate README for all
major directories with any major changes to existing directories noted (and all
READMEs should be able to be accessed from the website), all QA checks should pass,
there should be an appropriate license file,
code of conduct, contact details
(including a Slack channel) and things should just work.