Fix bug with capacity assertions being out of order in test suite results

[lukehesluke]

Fix issue relating to the order of test results within a test suite output page - sometimes the errors are not related to the relevant JSON output which can be confusing

[lukehesluke]

Nick believes that this happens only when C2/B fail. In these instances, the capacity assertion logs come out in the wrong order. First step: reproduce

[lukehesluke]

@nickevansuk I've tried the following things:

• Forcing an error at B by creating an invalid request
• Forcing an error at B by just throwing a random error
• Forcing an error at the assert opportunity capacity stage by expecting an incorrect capacity
• And likewise all of the above for C2

And in all cases, the capacity assertion log appears to be in the right place in the output .md file

[nickevansuk]

@lukehesluke have you tried a validation error at C2 or B, and seeing where that validation error is displayed (was that what "invalid request" above meant?)? Noting that validation errors and test failures are handled differently.