The ES compatibility tests are currently failing because the task response has changed between our lowest and highest ES versions, and we assert on the actual json returned. This is a new test, which is why we haven't seen it before.

We should make this test more robust going forward, that that it doesn't fail on response changes but also makes sure that task responses can be parsed during normal Optimize operation and upgrade