E2E test: expose test request details

[mflendrich]

per #869 (review)

During normal test runs, output is gobbled up by the validation check. Although I'd normally diagnose issues with incorrectly-written validation by reviewing curl's output, the test relies on printing the status code only, and I have to break out of the normal test flow and run components manually to get that. Trying to then work backwards to fix the test isn't perfect either, since the path to set up the test environment is different, and those differences may affect component behavior.

It sounds necessary to include more testing output (specifically: request and response info) in test results. Maybe in the test stdout/stderr, maybe in a file/directory saved by tests on disk.

Similar to #938. May be solved together.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.