Allow sentinel transitions to run synchronously against incoming SMS messages

[SCdF]

Currently the flow for an SMS with a default response is slower than it could be:

• CHW sends an SMS to the gateway, which takes it and puts it in it's queue
• Gateway wakes up every minute and sends the SMS to Medic, gets any existing SMS to send back and closes the connection
• Sentinel asynchronously updates the SMS report to add a default response
• 1 minute later Gateway talks to Medic, finds this response and sends it out.

We should look into extracting sentinel into a shared lib that we can run in realtime when receiving new SMS. This means we will any resulting SMS as part of the same request.

Combined with #4858 this could greatly increase the responsiveness of SMS.

[dianabarsan]

Being such a heap of work, I decided to break this up into multiple pieces:

• Remove Nano from Sentinel (610202a)
• Fix Sentinel transition bugs (The update_scheduled_reports transition runs indefinitely #5347, Registration transition invalidates unique ids when creating people #5345, The conditional_alerts transition should sort docs by reported_date #5357, The accept_patient_reports transition clears sent tasks #5390, The death_reporting transition does not process reports when submitter has no phone number #5359, Message recipient defaults to sender when recipient is explicit #5369, Registration transition should calculate dates relative to reported_date #5410, Link the report to the scheduled task that caused the report to be created #4694 (comment))
• Add E2E tests for every Sentinel transition (waiting for the last 2 issues described above to be fixed/approved and update their corresponding tests)
• Pulling all transitions out into a shared library
• Updating Sentinel to use Shared transitions
• Update API to apply transitions on incoming messages

[dianabarsan]

Ready for AT on 4857-detached-sentinel-bis branch.

[ngaruko]

LGTM.
Tested by sending a message via the admin portal and /api/sms and quickly moving to the app message tab to see the result. Messages are sent instantly.
Back to you @dianabarsan for merging!

[dianabarsan]

There is one new library to be published and updates to be made so the branch is using the new library. Will merge once I get to a good connection.