Fix several endpoints that no longer have <result> element wrapper. #25
Description
There was a bug in Rundeck pre-2.4.0 that caused some v11+ endpoints to be wrapped in the <result> element. This client was coded according to that bug.
If we simply remove the expectation that the <result> element is there then we break compatibility with Rundeck pre-2.4.0. Instead, let's see if we can add the header X-Rundeck-API-XML-Response-Wrapper: true to these endpoints to force the <result> wrapper.
Related issue in Rundeck project - rundeck/rundeck#1008