Add print test for error in middle of multipage job

Add a test which will have a rendering failure on a page before the end
of the job, where multiple pages have already been sent to the OOP
PrintBackendService.  This test needs to be disabled, as it shows there
is incorrect print control flow in PrintBackendService for this
scenario.

This only affects Windows, which has a rendering call per page instead
of just one rendering call for the whole document.  Update the testing
infrastructure to allow specifying that a rendering error can occur on
a particular page number.  Extend the class PrintBackendServiceTestImpl
to hold onto pages without immediate rendering, to ensure consistent
test behavior so there is no race condition between getting pages sent
before the service can process them.

LOW_COVERAGE_REASON=Files notified for are all browser tests support.

Bug: 1326580
Change-Id: I6a0ee1211ea4b911802372d4db1e2274a718af67
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3658629
Commit-Queue: Alan Screen <awscreen@chromium.org>
Reviewed-by: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1051920}

• chrome/browser/printing/print_backend_service_test_impl.cc[diff]
• chrome/browser/printing/print_backend_service_test_impl.h[diff]
• chrome/browser/printing/print_browsertest.cc[diff]
• chrome/services/printing/print_backend_service_impl.cc[diff]
• printing/test_printing_context.cc[diff]
• printing/test_printing_context.h[diff]