Print assertion phase when verifying rule result

[yuumasato]

When a rule's result doesn't match the expected result, let's also print the phase in which it happened, whether the default result or after remediation is applied.

[yuumasato]

This is just a small quality of life improvement.

When I'm checking out the e2e results I search for to the rule didn't match lines and consistently find myself scrolling up or down to figure out whether the scan I'm looking at is the before or after remediations...

[openshift-ci]

@yuumasato: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-aws-ocp4-moderate	cb2f055	link	true	/test e2e-aws-ocp4-moderate

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[yuumasato]

The moderate test failed, but that showcased the patch in action.

medium
    helpers.go:879: E2E-FAILURE: The expected remediated result for the e2e-moderate-resource-requests-limits-in-deployment rule didn't match. Expected 'PASS', Got 'FAIL'
    helpers.go:872: Result - Name: e2e-moderate-resource-requests-limits-in-statefulset - Status: FAIL - Severity: medium
    helpers.go:879: E2E-FAILURE: The expected remediated result for the e2e-moderate-resource-requests-limits-in-statefulset rule didn't match. Expected 'PASS', Got 'FAIL'