Pathfind: Improve Jenkins Integration pipeline

The integration pipeline needs some attention. It is extremely difficult to have all the integration tests succeed across all server versions we tests against as the Jenkins + cbdyncluster combination proves to be a difficult environment for consistency.

Something that can be frustrating w/ the Node.js tests is the output log is just the couchbase logger w/o the test info, so it is difficult to align the logs w/ tests that have failed. I have not looked in detail to the pipeline, but I wonder if moving to running `npx ts-mocha...` would be better than `npm run tests`? Also, as Jenkins goes might be nice to have the logs saved to a file and then we can download the file if/when needed (in the Python world I archive the file only on failure, or if the user opts to keep the log). Just a thought

• Potential updates to the Node.js test suite
  • Specifically around some mgmt APIs, there needs to be better mechanisms on ensuring indexes exist and that they are populated (at least populated enough to start running tests).