Queuing

[tylersamples]

As it currently stands we have the model for queuing but the TwilioController logic to insert the user and the pre-notification logic to check and dequeue logic has not been completed. Add documentation surrounding queuing.

Only support queuing to a case number if ExCourtbot is configure with case types. The rational for this requirement is simply to reduce the questioning round trips with the end user.

Only enable queuing if a queued_ttl_days is set. A infinite queued_ttl_days should not be supported.

The implementation must

General messaging flow:

• User texts service with an unknown case number (but the format matches a known case type)
• User receives response saying case number is invalid and we prompt them to see if they'd like to subscribe
• User responds yes
• Respond to user telling them they are subscribed and in queued_ttl_days the subscription will expire if we do not receive anything

Add tests to ensure the following cases:

• If a user subscribes, make sure a queue record is created
• If a user responds "UNSUBSCRIBE", make sure the queued record is removed
• If a user is subscribed and we import a hearing with that case number the user will receive a notification
  • If county duplication is enabled, we prompt the user to ask if it's the correct county
• If the queued_ttl_days elapses the queued record is removed

[tylersamples]

Queuing if exists is now supported. I'll add a new issue specifically for queuing if case type format is matched.