Shift parsing of question papers out of management command.

It's usually nicer for testing, etc, to have management commands
relatively thin so I'm shifting parsing of question papers to the
question_scraper module instead of directly in the management command.
Remove unused return values.
Use requests rather than urllib2.

I'd forgotten to import urllib2 when moving something, but let's
just get rid of it altogether and use requests instead.
Some PEP8ification of whitespace, etc.
Start big rewrite.

1) Rename regex variable to something more descriptive.
2) Use integers for parliament/session, etc rather than text,
   this will help us see them in order, and also gives an opportunty
   to deal with 'FOURT' where there should be 'FOURTH'.
3) First go at loop over matches
Remove tags from expected json test output.
Get spliting regex finding same number of questions as before.

This is done by starting to use a </b> rather than a colon as
our indication of the end of the intro.

We're now finding 104 questions, which is the same as in the
test output file.

However, there should be one more, question 720, which is getting
missed because of a unicode character in a name.

Strip out most <b> and <i> tags.
Switch on unicode in regex.

This finds us the last remaining question, the one asked by
Mrs D A Schäfer.
Replace entities in output with unicode.
Add missing question to expected output.

The scraper, and the expected output had both been missing a question
because it contained a unicode character (Mrs D A Schäfer).

Add this to the expected output, now that we're catching it.
Search for the question regex rather than splitting on it.

Also rename it to something more sensible.
Start collecting things to store as Question.
Add session matching stuff.

Not fully working yet, but coming along.

Remove fixme and unneeded code.

This is now handled by dropping the first two text elements on each
page.
TIDY: ALL SORTS
Avoid whitespace at ends of the question.
Use word characters rather than [A-Z]
Use </b> to indicate end of translated.
Make sure colon after the intro is after the </b>.

Since we're using the </b> to be the end of the intro, we could
do with the colon and </b> always being in the same order.
Allow extra text after colon in intro.

After the colon in the intro, we may need some extra text stating
that the question was originally oral.
Better expected output.

More consistent colons, and whitespace.