kobotoolbox: migrate to common 2.0

[josephjclark]

At the moment, kobotoolbox is version locked to common@1.15

This means it's still using and exporting the old axios HTTP helpers.

We can live with this for a while BUT a major problem here is that the docs for kobo will be wrong.

kobo docs says it exports http from common. If you click on http it'll show you the latest common docs, which use the new undici APIs. This is a lie.

What we need to do is:

• Remove axios from kobotoolbox
• Update kobotoolbox to the latest common (we usually use workspace:*)
• Re-write the kobo HTTP layer to use the new HTTP helpers in common (see commcare for an example - Utils.js wraps the common request helper to provide an easy HTTP API to commcare)

[josephjclark]

Hey @aleksa-krolls gotta flag this - I want to put out a common 2.0 adaptor in the next couple of days, but it'll introduce a documentation bug in kobo. I think we'll need to address this urgently by migrating kobotoolbox away from axios (which is a good thing anyway).

So I think someone will need to pick this up next week.

[josephjclark]

Ditto for progres and rapidpro actually. With those two I would rather remove the http export and put out a new major release. I'd rather break them than maintain them.