Improve testing on cht-conf

[njogz]

Describe the issue We currently do not have integration/e2e tests on cht-conf.

Describe the improvement you'd like Add some happy path tests to get started on this type of testing. Tests to add might include:

• a local edit through the actual cli
• starting up API and couch and ensuring the edits get pushed correctly

Describe alternatives you've considered None.

[njogz]

Refactor fetch-document-list.js to address this PR comment

[sugat009]

Updates: After a brief assessment of the current codebase of cht-conf and obtaining insights from @garethbowen , @andrablaj , @jkuester and @m5r , the e2e tests will be conducted for each action(backup-all-forms, backup-app-settings, etc.) available on cht-conf.

The e2e test plan will be roughly as follows:

1. Run a latest version cht-core instance using docker-helper at the beginning of the e2e test. This can be extended to include multiple supported versions of cht-core but for initial setup purposes we'll be running tests against the latest version only.
2. Run the cht-conf actions against the cht-core instance. Check if the output is as expected in that cht-core instance.
3. Stop the cht-core instance using the docker-helper.

Additionally, to make the reviews and feedback short and often, I plan on sending PR for each action. I've created a feature branch 425-improve-testing-on-cht-conf onto which I'll be sending the PR for each action. Let me know if there's anything.