This was noticed when investigating why errors are not causing the test to fail. It's not clear if this is related to the problem, but the existing logic was definitely atypical.
* Update istio version for testing
* Framework changes in base istio required changes
* Work on whitelist
* Remove whitelist and move to a new feature
* Another istio.io/istio update
* Another framework change - remove test suite name