feat(#9544): add offline freetext search indexes

[jkuester]

Description

Closes #9544

Code review checklist

• Readable: Concise, well named, follows the style guide, documented if necessary.
• Tested: Unit and/or e2e where appropriate
• 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.

[jkuester]

This is the only real change here. The rest is just a quick re-factor to use async/await.

[jkuester]

These changes in shared-libs/search are just temporary. The proper changes will need to be made against the cht-datasource code once we re-base on top of that.

This is why I have not added any additional unit tests to cover this logic (or worried too much about code structure).

[jkuester]

We will need to remove this once the medic-client/contacts_by_freetext view is deleted, but for now I thought it was useful to keep this in here to prove that the new offline indexes behave exactly the same as the original ones.

[jkuester]

c.c. @m5r and @tatilepizs Particularly regarding how I have updated the e2e search tests to run both for an online and an offline user. I think this means these same tests can cover the offline indexes and the new Lucene functionality. 👍

[jkuester]

This bootstrapper code gets run during the main initialization of the app (before any of the Angular code spins up. This bootstrapping gets run during initial login and also when reloading the app (e.g. when the webapp-code/app-settings/ddocs change).

So, any time in the future when we make updates/additions/removals of views here, we can be confident that everything will be initialized properly in the local db when the app reloads.

[m5r]

Nothing to add to Sugat's comments. I left an open-ended question about warming up views in the bootstrapper but it's not a blocker

[jkuester]

For clarity, this PR is now is now blocked waiting on #9541. They should both be merged together before going to master. We cannot ship this one earlier because it would involve adding new offline indexes without actually removing the existing indexes that exist both online and offline. The effect would be to double the amount of space used on offline devices by the freetext indexes....