style(animator): style cleanup
chore(revert): Revert accidental change to showdown

Offending SHA: 0b6f1ce5f89f47f9302ff1e8cd8f4b92f837c413
chore(revert): accidental inclusion of nonexistent test.

Offending SHA: 0b6f1ce5f89f47f9302ff1e8cd8f4b92f837c413
fix(ngShow/ngHide): revert to display:'' for show

Regression introduced by ngAnimation
SHA: 0b6f1ce5f89f47f9302ff1e8cd8f4b92f837c413
feat(Scenario): autodisable animations when running e2e tests

animations cause the dom to contain elements that have been removed
from the model but are being animated out.

we could teach the e2e runner to wait for animations but that would
make all tests slower. it should be quite safe to just disable
animations automatically when the app is running via the e2e test
runner.

this change disables only css animations. we should make additional
change that disables js animations as well, but since we don't need
this right now I'm punting on it.
chore(karma): upgrade karma to 0.8.4

we needed this upgrade to disable animations in scenario runner
(karma ships with its own copy of angular-scenario.js which
got update in 0.8.4)
docs: add animations into docs and directive examples