WIP: speed up acceptance tests by using correct Capybara matchers.

Instead of:

  expect(..).not_to have_css(..)

now we use:

  expect(..).to have_no_css(..)

this way the Capybara matcher should immediately return, instead of waiting a few seconds to see if the passed CSS appears.

Inspired by this blog post:

http://blog.codeship.com/faster-rails-tests/
Similar to 9b631b10a8146b15c2a4e6f411dad6baf0506db9 but replacing:

  expect(..).not_to have_text(..)

with:

  expect(..).to have_no_text(..)
Similar to commit 9b631b10a8146b15c2a4e6f411dad6baf0506db9 but replacing:

  expect(..).not_to have_content(..)

with:

  expect(..).to have_no_content(..)
Use Poltergeist (based on the headless webkit-based PhantomJS browser) for testing, instead of capybara-webkit.

It is supposed to be faster, we'll see.

Phantomjs does not need a virtual framebuffer, so the lines that started xvfb in Travis CI have been removed.

Poltergeist currently does not support url blacklisting, which we added back in commit 7ba7af3f7af11b90a754769ac36824f53817b2cb, so the lines that configured url blacklisting have been commented. There is a PR waiting merge in the Poltergeist github repo, so these lines will probably be uncommented again in the future.

For the moment Poltergeist is configured not to raise Ruby errors when a javascript error happens, to ease transition from capybara-webkit to poltergeist. This may change in the future.
Removed the line that installed the bundler gem before running tests in Travis CI.

This was necessary in the past because Travis VMs had an outdated Bundler version. It should no longer be necessary, removing it will save a bit of time in the CI environment.
Revert "Use Poltergeist (based on the headless webkit-based PhantomJS browser) for testing, instead of capybara-webkit."

This reverts commit 663778bbefc9a6be50793d0447521c2bdb7efc18.

Conflicts:
	.travis.yml