Polyfill window.crypto.getRandomValues in tests

[garrettjstevens]

fixes #2794

The polyfills window.crypto.getRandomValues in the tests since it isn't implemented in JSDOM.

[cmdcolin]

do you think it will throw errors in @jbrowse/img or other nodejs usages since it is only polyfilled under jest? could add the polyfill to the jbrowse-img product

it's tricky to test what @jbrowse/img how it will end up installed for the end-user so I can't easily verify

[garrettjstevens]

Are OAuth tracks intended to be supported with @jbrowse/img? I'm not sure how that would work since there's no UI for entering credentials.

[cmdcolin]

It is not necessarily intended but perhaps if we really wanted to we could find a way to supply the auth token manually via the command line. Since @jbrowse/img is so deeply intertwined with @jbrowse/react-linear-genome-view and @jbrowse/react-linear-genome-view does not use @jbrowse/plugin-authentication it is probably not a concern for now though

[cmdcolin]

also note: my concern for mentioning it was more that whenever this code is instantiated, the getRandomValues automatically runs whether or not the oauth is used (which is why there are many console.logs with the error on main)

[cmdcolin]

can merge this for now :)