Rearranging UpdateHeaderForm for clarity

Moving methods to be closer to their relevant collaborators
Removing TODO as it was answered

See the immediate line below; I'm capturing the exception's message
and persisting that on the doi_creation_request

[skip ci]
Teasing out magic strings
Moving array wrap to later in the cycle
Teasing out update methods from Job

Pushing the persistence interaction methods down to the Repository
layer.
Adjusting DoiRequestCreation to include defaults

Both the database and ActiveRecord are enforcing this behavior, as
relying on ActiveRecord is the path of folly.
Deferring to initial state
Adding a spec:featureless task

I want to see how well my unit tests are covering all of the
code-base. To do this, I'm avoiding running the feature tests as I've
been relying on them to catch a few things; And while that is good, I
would like a bit more isolation.
Covering a few untested methods

The spec:featureless task revealed that the AuthorizationLayer had
some missing code coverage. Remedying that behavior.