ensure we do not reuse logins in factories

prevent random failures. We use transactional fixtures so this is not as much of an issue as is used to be. However Faker will sometimes create logins like aaron - which we already have in the fixtures.
add simple integration test for discussion_page

Also bring back screenshots when integration tests fail...
we reset the defaults during setup because we rely on the
driver and the session in the enhanced_logging module.

Also note the fancy hover_and_edit method for clicking on the
shy edit links.
basic wiki page integration test with versions
basic integration test for rate-many and ranked-vote
fix assert_no_content - has_no_content is different from \! has_content

both will wait to see if their condition becomes true through ajax. So while \!has_content will return false if the content is still present has_no_content will wait for the content to disappear.
only add style block in header if there's content for it
tune ranked vote integration test some
add task list page integration test
basic asset_page integration test
gallery page integration test w/ some images

also navigating the gallery some.
fix non deterministic issue with wiki integration test

So what was going on here...

we were clicking on the edit link, filling in the form and then clicking on submit.
But sometimes the page had not loaded the edit form after we clicked on the link so we would fill the textarea already loaded. Then the new textarea would be loaded and we would click submit for an empty form.

lesson learned: always wait for what you clicked on.

Actually we should prevent the same thing in the ui. But that is for later.
only one translation for image_count keys

CI was picking a different one then my dev env... strange.
Merge pull request #58 from azul/test/page-integration-tests

page integration tests