fix(server): Fix 5.0 spec duration always reporting as 0ms

[kuceb]

exists only in develop
fixes bug introduced by #8148 causing spec durations to be printed as 0ms in the final spec results.

fix #8309 (unreleased)

before:

after:

[cypress-bot]

Thanks for taking the time to open a PR!

• Create a Draft Pull Request if your PR is not ready for review. Mark the PR as Ready for Review when you're ready for a Cypress team member to review the PR.
• Become familiar with the Code Review Checklist for guidelines on coding standards and what needs to be done before a PR can be merged.

[cypress]

---

Test summary

8126 • 0 • 108 • 3

---

Run details

Project	cypress
Status	Passed
Commit	1aa178c
Started	Aug 18, 2020 8:27 PM
Ended	Aug 18, 2020 8:33 PM
Duration	06:36 💡
OS	Linux Debian - 10.2
Browser	Multiple

View run in Cypress Dashboard ➡️

---

This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard

[chrisbreiding]

Looks like we do have a number of tests that take 0ms...

[bahmutov]

the tests are too fast ...

[chrisbreiding]

Looks like it happens when the tests don't even run because of a syntax error or plugins file error.

[bahmutov]

@bkucera is this a wrong return from module API? maybe the module API test could just confirm it?

[kuceb]

I requested the review too early, I'm fixing these now