Adding micromachine for state machine behavior
Initial commit for ETD Student Submission
Adding ETD Student Submission Cycle

As with all artifacts they age and rust
Enhancing the existing state machine
Renaming state events
Adding policy question lookup based on state
Adding Sipity::Models::Header#processing_state

What is a processing_state? The SIP is working its way to becoming an
AIP. I'm envisioning a singular workflow for a given header. The
workflow is responsible for moving the data towards completion. And
we persist the processing_state of the data as its moving to and from
disk.
Updating micromachine gem

I want to know the triggering event's name.
Adding repository methods as a placeholder
Working on EtdStudentSubmission state_machine

To consider, how is this any different from a runner? It is managing
to encapsulate logic, much like a job. Consider how the state machine
would apply to the DOI job.
Appeasing rubocop

Also teasing out what is happening as part of the building of the
state machine.
Removing methods that need be there
Merge branch 'adding-state-machines'

* adding-state-machines:
  Removing methods that need be there
  Appeasing rubocop
  Working on EtdStudentSubmission state_machine
  Adding repository methods as a placeholder
  Updating micromachine gem
  Adding Sipity::Models::Header#processing_state
  Adding policy question lookup based on state
  Renaming state events
  Enhancing the existing state machine
  Adding ETD Student Submission Cycle
  Initial commit for ETD Student Submission
  Adding micromachine for state machine behavior