[CLN] JavaScript Client Tests

[atroyn]

Our JS / TS client tests are currently pretty messy. There doesn't seem to be a clear way to run them locally (running bin/ts-integration-test results in failures which don't appear on the GitHub workers / in CI), and the functionality of the tests is distributed across many files.

Additionally, it does not seem that the JS tests generate a new JS client (see #2412), and they probably should for correct coverage.

It would be good to unify theses tests, make sure they are replicable locally and on CI.

[atroyn]

@AlabasterAxe we might want to take a look at this as part of the current milestone, since we will be modifying JS probably a lot.

[AlabasterAxe]

@atroyn I think that a lot of the clutter for the existing tests arises out of setting up and tearing down the test environments. I put together this proof of concept PR which moves the environment setup and teardown into the JS test code:

https://github.com/AlabasterAxe/chroma/pull/5/files?diff=split&w=1

this would allow us to run all of the tests together instead of having to do separate environment setups and teardowns across several jest runs for the various auth configurations

Thoughts?

[AlabasterAxe]

Also, I have this PR which just gets that integration test script running locally: #2518