WX-1339 Make throwExceptionOnExecuteError false for PAPI aborts

[aednichols]

Adding setThrowExceptionOnExecuteError(false) call causes execution flow to go into the path we want that inspects the error more precisely in handleGoogleError.

I tested this by deliberately breaking the request so it always gets a 400 back. With the existing code, the log looks just like what we see in prod:

2023-11-01 19:54:12 cromwell-system-akka.dispatchers.backend-dispatcher-91 WARN  - PAPI request worker had 2 failures making 5 requests: 
400 Bad Request
POST https://lifesciences.googleapis.com/v2beta/projects/1005074806481/locations/us-central1/operations/6175597626605185257:cancel
{
  "code": 400,
  "errors": [
    {
      "domain": "global",
      "message": "Invalid JSON payload received. Unexpected token.\nasdf\n^ Payload appears to be compressed. It may either be corrupt or uncompressed data may be too large for the server to handle.",
      "reason": "parseError"
    }
  ],
  "message": "Invalid JSON payload received. Unexpected token.\nasdf\n^ Payload appears to be compressed. It may either be corrupt or uncompressed data may be too large for the server to handle.",
  "status": "INVALID_ARGUMENT"
}

---

Changing throwExceptionOnExecuteError to false, we see that we no longer throw an exception and we get the expected "no longer running" message in the log!

2023-11-01 19:57:48 cromwell-system-akka.dispatchers.backend-dispatcher-162 INFO  - PAPI declined to abort job projects/1005074806481/locations/us-central1/operations/5250112889402522122 in workflow b70eafc9-66a7-4b22-b9bc-621c22b5a4ed, most likely because it is no longer running. Marking as finished. Message: Invalid JSON payload received. Unexpected token.
asdf
^ Payload appears to be compressed. It may either be corrupt or uncompressed data may be too large for the server to handle.

[jgainerdewar]

🎉

[THWiseman]

Excellent find, nice work!