add improved error messaging in Worker class

[OVI3D0]

Description

Adds more detailed error messaging to the console if a request fails or if a workload is improperly configured.

Example:

[ERROR] Cannot execute-test. Benchmark operation failed:
Worker ID: 0
Task: index-statrs
Workload: geonames
Test Procedure: append-no-conflicts
Cause: Unknown
Error: No runner available for operation type [index-statrs]

Issues Resolved

#715

Testing

• New functionality includes testing
  make test

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[IanHoang]

This is clearer but one other step we should consider keeping track of a running list of "causes" that Worker Coordinator commonly encounters. I'm not sure how descriptive these causes are in the exception e but if we find a correlation between a cause and something like the way the OSB cli was set up, we should suggest a potential fix for the user.

[OVI3D0]

This is clearer but one other step we should consider keeping track of a running list of "causes" that Worker Coordinator commonly encounters. I'm not sure how descriptive these causes are in the exception e but if we find a correlation between a cause and something like the way the OSB cli was set up, we should suggest a potential fix for the user.

This makes sense and could give the user a better sense of where they can make a fix to stop the error and run a benchmark. Even in the example, No runner available for operation type ... is a bit ambiguous and a newer user might not know they misspelled the name of an operation.