Add diagnostics to ConsensusQueue in handle validation tests

[Abe27342]

Description

Modifies ConsensusQueue's generic "store a piece of data" implementation in handleValidation.ts to give more information on a couple theoretical error methods. This test timed out on a recent tinylicious run where based on telemetry, it seems like the test got past the point of loading the 2nd container. Thus it was likely a deadlock awaiting this promise. I've been unable to reproduce this behavior locally. The goal here is to get information about the failure mode the next time this race condition happens.

[jzaffiro]

Looks good!

[msfluid-bot]

⯅ @fluid-example/bundle-size-tests: +245 Bytes

Metric Name	Baseline Size	Compare Size	Size Diff
aqueduct.js	460.93 KB	460.96 KB	⯅ +35 Bytes
azureClient.js	559.03 KB	559.08 KB	⯅ +49 Bytes
connectionState.js	680 Bytes	680 Bytes	■ No change
containerRuntime.js	261.68 KB	261.69 KB	⯅ +14 Bytes
fluidFramework.js	401.58 KB	401.6 KB	⯅ +14 Bytes
loader.js	134.17 KB	134.19 KB	⯅ +14 Bytes
map.js	42.43 KB	42.44 KB	⯅ +7 Bytes
matrix.js	146.64 KB	146.65 KB	⯅ +7 Bytes
odspClient.js	526.18 KB	526.23 KB	⯅ +49 Bytes
odspDriver.js	97.8 KB	97.82 KB	⯅ +21 Bytes
odspPrefetchSnapshot.js	42.76 KB	42.78 KB	⯅ +14 Bytes
sharedString.js	163.32 KB	163.33 KB	⯅ +7 Bytes
sharedTree.js	392.05 KB	392.05 KB	⯅ +7 Bytes
Total Size	3.3 MB	3.3 MB	⯅ +245 Bytes

---

Baseline commit: d45e3ea

Generated by 🚫 dangerJS against ae75729