[BUG] Fix JS client regression

[ibratoev]

Fix regression that stopped running the JS client unit tests during CI.

Both regressions are from a large PR: #1970.

[github-actions]

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

• Can you think of any use case in which the code does not behave as intended? Have they been tested?
• Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
• If appropriate, are there adequate property based tests?
• If appropriate, are there adequate unit tests?
• Should any logging, debugging, tracing information be added or removed?
• Are error messages user-friendly?
• Have all documentation changes needed been made?
• Have all non-obvious changes been commented?

System Compatibility

• Are there any potential impacts on other parts of the system or backward compatibility?
• Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

• Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

[tazarov]

Looks good. Thank you @ibratoev !!! Good catch

[ibratoev]

It seems a GO test failed. I looked into the test and the issue is that in the GO metastore collection tests, a particular order for collections is expected. The collections are currently returned ordered by id which is UUID -> random. This makes the test flaky and should fail every second run.

I will prepare a quick fix.

[beggers]

Thank you @ibratoev ! This was a miss on my part -- I appreciate the thoroughness.

The Golang tests are flaky right now and we're working on them. I'm happy to merge this without them.