update and test Cromwell 32 with Google PAPI v2

[dpark01]

Cromwell version 32 starts the transition from PAPIv1 to PAPIv2 and signals the future deprecation some of the old "JES" terminology (the predecessor to PAPI). Our current template Cromwell config file uses this old terminology (and PAPI v1).

We should update our Cromwell template to utilize PAPI v2, keeping in mind that:

• We currently have no automated testing for Cromwell-on-GCE (Travis executes Cromwell-on-local only). So we'll have to test results manually in something like the gcid-viral-seq GCP project.
• We already know that our docker container fails on PAPI v2 unless we increase the boot disk above it's default 10GB size (for example, with dsub we need to specify --boot-disk-size 20).

Cromwell version 32 in viral-ngs is pending the merge of #838 .

[tomkinsc]

It appears that with WDL 1.0 we can specify the bootsize as part of the runtime block:

runtime {
  bootDiskSizeGb: 50
}

[dpark01]

Hm... although dxWDL does not yet support WDL 1.0, I think it ignores runtime attributes it doesn't recognize, so maybe we can use this...