Add examples/lots_of_warnings.yml

This playbook causes ansible-lint to output tons of warnings;
enough to exceed typical stdout buffering size and thus to show the need
for catching IOError (EPIEP) errors.
Don't print traceback on EPIPE

Without this, you will get a traceback if you pipe to `head` for
example:

```
$ ansible-lint ~/dev/surveymonkey/smstack/vagrant.yml | head
...
Traceback (most recent call last):
  File "/Users/marca/dev/git-repos/ansible-lint/py27.venv/bin/ansible-lint", line 10, in <module>
    execfile(__file__)
  File "/Users/marca/dev/git-repos/ansible-lint/bin/ansible-lint", line 78, in <module>
    sys.exit(main(sys.argv[1:]))
  File "/Users/marca/dev/git-repos/ansible-lint/bin/ansible-lint", line 73, in main
    print formatter.format(match)
IOError: [Errno 32] Broken pipe
```
Merge pull request #11 from msabramo/no_traceback_on_EPIPE

Don't print traceback on EPIPE