chore: do not run Couch container for unit tests

[jkuester]

Description

Currently, the cht-conf unit tests spin up a Couch docker container before the tests run and then tear it down at the end. It turns out that Couch instance was only being used in 2 test files:

• The move-contacts.spec.js needed it originally. It could not use a local Pouch instance because of limit and skip view query options are ignored when keys are used, if the adapter is not http pouchdb/pouchdb#8370. However, that issue was fixed and our current Pouch version includes the fix! So, I have updated these tests to just use a local Pouch instance.
• The newer session-token.spec.js was actually originally slotted as an "e2e" test, but we moved it to be an "integration" test when we added proper e2e tests. After digging into this more, it seems to me that this can just be a full e2e test. It technically does not need an entire CHT suite running, but since we are spinning one up anyway for the other e2e tests it is actually less work (and less code to maintain) if we just make it an e2e test.

Code review items

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

License

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

[jkuester]

Apparently GitHub is not smart enough to realize that this is a modified version of the test/integration/session-token.spec.js file. I am afraid you will have to manually diff this to see what actually changed in the file....

(TLDR is that I was able to remove a lot of code.)

[m5r]

Perfect! Thanks for cleaning up those tests