Adding conditional to make sure fast specs exist
Adjusting Rakefile to use existing constant
Adding tasks for batch profile querying
Stubbing out offline task behavior
Extracting Orcid::Runner

Given that I want to make a second Runner for profile creation
I opted to extract the Orcid::Runner class
Marking Orcid::NamedCallbacks as "fast"

Run `./script/fast_specs` to run most of the unit tests that don't
require Rails ecosystem
Extracting fast specs
Updating Orcid::Profile to be a fast_spec
Adding StubCallback to spec support
Replacing BasicObject inheritance

This was causing some unexpected behavior in some tests. Removing
BasicObject infavor of Object
Tweaking Remote::ProfileCreationService

I'm trying to move the callbacks onto the the service as it is the one
that has the best handle of states.
Removing debugger for Rakefile

[skip ci]
Extracting #default_profile_creation_service method

I believe I can get just as much bang for my buck out of this class.
Adding spec:all
Adding simplecov
Removing Forwardable & HashWithIndifferentAccess

Leaning on ActiveSupport and marking things as not fast spec
Updating ProfileRequest to leverage callbacks
Adding orcid:batch:create
Adding another file to fast spec
Merge branch 'adding-rake-tasks-for-batch'

* adding-rake-tasks-for-batch:
  Adding another file to fast spec
  Adding orcid:batch:create
  Updating ProfileRequest to leverage callbacks
  Removing Forwardable & HashWithIndifferentAccess
  Adding simplecov
  Adding spec:all
  Extracting #default_profile_creation_service method
  Removing debugger for Rakefile
  Tweaking Remote::ProfileCreationService
  Replacing BasicObject inheritance
  Adding StubCallback to spec support
  Updating Orcid::Profile to be a fast_spec
  Extracting fast specs
  Marking Orcid::NamedCallbacks as "fast"
  Extracting Orcid::Runner
  Stubbing out offline task behavior
  Adding tasks for batch profile querying