Create configuration so new ORA can know where to log non-XBlock events to

@wedaly, @stephensanchez: This is the last bit of TIM-260, and is necessary for event information to go through for scoring (our only non-XBlock tracking event).

@rocha, @mulby: As discussed, the event lacks a lot of the normal fields. An example:

```python
{
    'points_possible': 8L,
    'points_earned': 8L,
    'event_type': 'openassessment.workflow.score',
    'submission_uuid': u'977f453e-b6f1-11e3-a909-080027880ca6'
}
```

I'm working this weekend but out starting on Monday, so either @wedaly or @stephensanchez will need to shepherd this through if there are other changes.