Fix RequestService test sometimes failing in CICD

[alexandrevryghem]

Description

Because tests are executed slower on CICD it can sometimes take one second or more to execute the RequestService#setStaleByHref(href), when the test arrives inside the subscribe, a create new RequestStaleAction with the current time is created (this can already be a few seconds after RequestService#setStaleByHref(href) was called). To prevent such errors we can just expect that lastUpdated will be a number instead of comparing the actual values. The purpose of that test is to check the type of RequestUpdateAction returned by the function and not the date when it was created, so this doesn't have any side effects. This is an example of such a failure.

Checklist

• My PR is small in size (e.g. less than 1,000 lines of code, not including comments & specs/tests), or I have provided reasons as to why that's not possible.
• My PR passes ESLint validation using yarn lint
• My PR doesn't introduce circular dependencies (verified via yarn check-circ-deps)
• My PR includes TypeDoc comments for all new (or modified) public methods and classes. It also includes TypeDoc for large or complex private methods.
• My PR passes all specs/tests and includes new/updated specs or tests based on the Code Testing Guide.
• If my PR includes new libraries/dependencies (in package.json), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
• If my PR includes new features or configurations, I've provided basic technical documentation in the PR itself.
• If my PR fixes an issue ticket, I've linked them together.

[tdonohue]

👍 Thanks @alexandrevryghem for tracking this down, as I've seen this random failure as well.

This seems like a reasonable fix, so I'll merge it immediately as it only impacts the specs.

[dspace-bot]

Successfully created backport PR for dspace-7_x:

• [Port dspace-7_x] Fix RequestService test sometimes failing in CICD #2564