Adding authentication logic to BaseRunner

I want to push this logic into the BaseRunner instead of the
controller as it provides an easier means for avoiding around filter
behavior.
Adding CitationsRunner authentication enforcement
Adding user sign in for feature tests
Adding authentication enforcement to DOIRunners
Adding HeaderRunners requires_authentication
Fixing yard output

[skip ci]
Ignoring yard documentation in repo

[skip ci]
Adding a test to verify API of Citation submit

This commit is verifying that the submission returns a truthful value.

This may not be the correct object to return on submission, but it is
better given the form API submit.
Merge pull request #8 from ndlib/adding-form-spec-verification

Adding a test to verify API of Citation submit
Merge pull request #7 from ndlib/adding-ignore-documentation

Ignoring yard documentation in repo
Merge pull request #6 from ndlib/adding-authentication-required

Adding authentication required
Adding Sip::Decorators documentation

[skip ci]
Moving decorators into a sub-directory

As I was looking at Sipity's documentation at
http://www.rubydoc.info/github/ndlib/sipity/master, I was noticing
that all of the decorators are in the main namespace. Which means that
there are, at this point 5 concepts in the main Sip namespace that
may not be immediately obvious.

So I've opted to move the decorators into a sub-directory. This
then creates a logical place to document the Decorators module.
Merge pull request #9 from ndlib/moving-concepts-into-sub-modules

Moving Decorator concepts into a module
Adding Sip::Forms documentation

[skip ci]
Moving Forms into subdirectory

As I was looking at Sipity's documentation at
http://www.rubydoc.info/github/ndlib/sipity/master, I was noticing
that all of the forms are in the main namespace. This meant that there
were quite a few concepts being exposed without proper introduction.

So I've opted to move the `forms/sip/forms` into a sub-directory. This
then creates a logical place to document the Sip::Forms module and
provide a proper introduction to the concepts.
Merge pull request #10 from ndlib/moving-forms-into-subdirectory

Moving forms into subdirectory
Adding documentation for Runners

[skip ci]
Moving Runners into a subdirectory

As I was looking at Sipity's documentation at

http://www.rubydoc.info/github/ndlib/sipity/master, I was noticing
that all of the runners are in the main namespace. This meant that
there were quite a few concepts being exposed without proper
introduction.

So I've opted to move the runners into `runners/sip/runners` into.
This then creates a logical place to document the Sip::Runners module
and provide a proper introduction to the concepts.
Merge pull request #11 from ndlib/moving-runners-into-subdirectory

Moving runners into subdirectory