test,report: relax CPU match requirements

Some CPUs have variable speeds, and so exact matches between what
`os.cpus()` and the report feature yield cannot always be expected:

```
> const results = []
> setInterval(() => results.push(os.cpus().map(({ speed }) => speed)), 1)
[...]
> results
[
  [ 1198, 1150, 1195, 1149 ],
  [ 1198, 1150, 1195, 1149 ],
  [ 1198, 1150, 1195, 1149 ],
  [ 1198, 1150, 1195, 1149 ],
  [ 2401, 2420, 2429, 2413 ],
  [ 2401, 2420, 2429, 2413 ],
  [ 2401, 2420, 2429, 2413 ],
  [ 2401, 2420, 2429, 2413 ],
  [ 2401, 2420, 2429, 2413 ],
  [ 2401, 2420, 2429, 2413 ],
  [ 2401, 2420, 2429, 2413 ],
  [ 2596, 2401, 2699, 2555 ],
[...]
```

Refs: nodejs#28829

test/common/report.js

@@ -109,7 +109,7 @@ function _validateContent(report) {
     assert.strictEqual(typeof cpu.idle, 'number');
     assert.strictEqual(typeof cpu.irq, 'number');
     assert(cpus.some((c) => {
-      return c.model === cpu.model && c.speed === cpu.speed;
+      return c.model === cpu.model;
     }));
   });
   assert.strictEqual(header.host, os.hostname());