Sequencer configuration in JSON should be keyed by name, not array

The JSON configuration for the sequencers is basically an array of nested documents, where each nested document represents a sequencer configuration. This is proving difficult to manage, as replacing a sequencer configuration becomes very difficult. The sequencer configurations must have unique names, so we should change the JSON Schema to not be an array but rather just be fields using the sequencer names.