test: don't hardcode timeout interval and don't rely on jasmine

[paul-soporan]

What's the problem this PR addresses?

#4543 hardcoded the timeout interval, but it has already gotten out of sync due to #3669.

How did you fix it?

Made it use jasmine.DEFAULT_TIMEOUT_INTERVAL Extracted the timeout to pkg-tests-core and removed usage of jasmine.DEFAULT_TIMEOUT_INTERVAL to make it easier for us to switch to jest-circus, the new jest runner.

I also added a TODO so that we don't forget to recheck whether this is still needed. (I have a feeling that the big-endian PR might've fixed all timeout issues).

Checklist

• I have read the Contributing Guide.

• I have set the packages that need to be released for my changes to be effective.

• I will check that all automated PR checks pass before the PR gets reviewed.

[arcanis]

Is jasmine.DEFAULT_TIMEOUT_INTERVAL available under jest-circus, the new Jest test runner that's been made the default?

[paul-soporan]

It's not, I updated the tests to not rely on jasmine (my BE PR used jasmine.DEFAULT_TIMEOUT_INTERVAL).

Will look into switching our tests to jest-circus in a different PR.

[merceyz]

Will look into switching our tests to jest-circus in a different PR.

Updating Jest would do that automatically.

[paul-soporan]

Yep, I'll work on upgrading jest and gradually enabling new features to see how much it improves things.