Improve logging in addons test

[ocofaigh]

The team are reporting that its very hard to debug some failures when the addons test fails. Below is some feedback we got (full log):

• It says Stack Deploy Failed, current state: draft however the only remaining member is reporting deploy-arch-ibm-slz-ocp-rmtwj9 is in state draft, not triggered, no changes, continuing assuming still deploying. So it would seem nothing actually failed here? Can we update the logging to maybe print exactly what triggered the failure here? What api was used to determine the failure here and what status value was returned? Maybe we should log that info?

• Since the test failed, the delete process was triggered and so the projects and all related workspaces were deleted. So we really have no way to know why this test failed without extra logging.

• We should not be logging this line: [TestAddonConfigurations] TEST EXECUTION END: TestAddonConfigurations - RESULT: PASSED. The test did not pass.

• Can we stop using the word "error" in the below logging? People tend to search for the string "error" in the logs for actual errors so suggest to use a different word for these log lines as they are not actually errors: