Fix parallel run durations + data passing, Should-Invoke mock error name, and ForEach null suggestion

[nohwnd]

Four recent 6.0.0 reports:

• Parallel total durations — container durations were summed, which overstates a parallel run since files overlap. Use the wall-clock duration (RunEnd − RunStart) for Run.Duration and leave the per-phase totals blank in parallel mode. Fix [v6 Parallel] Total durations are wrong #2794
• Pass data to parallel runs — Run.Parallel sent only the file path to each worker, so New-PesterContainer -Path … -Data @{…} dropped its data and parametrized files failed discovery on missing mandatory params. Workers now rebuild a data-bearing container when data is present. Fix Pass data to parallel runs #2793
• Should-Invoke error — the "could not find mock" message said Should -Invoke. Now Should-Invoke. Fix Error message reference wrong command when tests use Should-Invoke #2792
• Empty/null -ForEach — the throw now also points at Run.FailOnNullOrEmptyForEach, not just -AllowNullOrEmptyForEach. Fix Suggest local and global option for suppressing null in the failure #2782

Added parallel duration + data tests and tightened the mock/ForEach tests. The 3 unrelated SkipRemainingOnFailure test failures are pre-existing on main.

[nohwnd]

Split into four focused PRs, one per issue, since these are independent fixes:

• Fix parallel run total durations #2802 — parallel run total durations ([v6 Parallel] Total durations are wrong #2794)
• Pass data to parallel runs #2803 — pass data to parallel runs (Pass data to parallel runs #2793)
• Fix command name in Should-Invoke not-found error #2804 — Should-Invoke not-found error name (Error message reference wrong command when tests use Should-Invoke #2792)
• Suggest both local and global option in empty/null ForEach error #2805 — empty/null -ForEach suggestion (Suggest local and global option for suppressing null in the failure #2782)

Closing this in favor of those.