fix(#9467): quick fixes to RapidPro

[dianabarsan]

Description

• when api/v2/broadcast responds with 400, set the status as failed, so API doesn't retry sending the same message. This fixes incorrect phone number messages trying to be sent over and over.
• when api/v2/broadcast responds with 200, but without a status update, set the state to queued to fix message duplication (https://forum.communityhealthtoolkit.org/t/duplication-of-messages-in-textit-rapidpro/4047/19).

#9467

Code review checklist

• Readable: Concise, well named, follows the style guide, documented if necessary.
• Documented: Configuration and user documentation on cht-docs
• Tested: Unit and/or e2e where appropriate
• Internationalised: All user facing text
• Backwards compatible: Works with existing data and configuration or includes a migration. Any breaking changes documented in the release notes.

Compose URLs

If Build CI hasn't passed, these may 404:

• Core
• CouchDB Single
• CouchDB Cluster

License

The software is provided under AGPL-3.0. Contributions to this project are accepted under the same license.

[garethbowen]

Looks good to me. I'll make sure this gets a branch release so itech can try it out, and make sure it gets in to the 4.14.0 release.

[garethbowen]

We could also handle 403, and 404, more gracefully because both probably require manual intervention to fix so there's no point spamming RapidPro. Even 429s could be handled more gracefully.

But let's raise a new issue to handle these other cases because they're more temporary than the 400 being dealt with here because 400 is permanent failure.