Updating Etd Student Submission specs
Tweaking hound settings for state machines

The state machines are complicated objects with lots of methods and
due to how the implementation of the state machine, there are
complications.
Adding event triggers that auto advance
Rearraning spec location

It makes more sense for this spec to be in the other state.
Restoring code coverage
Adding #assign_group_roles_to_entity
Removing duplicate state

Thank you @dbrower for pointing out the redundant states
Adding after_successful_trigger!

Given that the state machine does not take action on events I want to
have the after after_successful_trigger! fire
Updating ETD documentation
Changing event_name structure
Renaming submit_for_ingest to submit_for_review

This is more descriptive of what is happening.
Adding Repository#send_notifications

These are placeholder methods
Adding some of the email notifications
Teasing apart what was becoming a very large method