fix(getport): Randomize first port using crypto

[noseworthy]

The current implementation of getPort() relies on using Date.now()to get the first port to try to launch mongo on, even when the EXP_NET0LISTEN flag is set. This causes a couple issues:

• If the Date module is mocked, it can result in getFreePort() returning the same first port every time.
• If multiple mongos are being started at once in parallel, it's possible for the same first port to be picked leading to port conflicts

In order to better randomize the initial port selection so that port conflicts can be avoided, instead of using Date.now() for an initial seed, use crypto.randomInt() which should provide more randomness and hopefully avoid some of these race conditions.

Related Issues

• 827

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (f5c7e27) 91.22% compared to head (b84c82a) 91.24%. Report is 3 commits behind head on master.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## master #844 +/- ## ========================================== + Coverage 91.22% 91.24% +0.01% ========================================== Files 15 15 Lines 1984 1988 +4 Branches 499 501 +2 ========================================== + Hits 1810 1814 +4 Misses 165 165 Partials 9 9 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[github-actions[bot]]

:tada: This PR is included in version 9.1.5 :tada:

The release is available on:

• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot :package::rocket: