Fix: resources: use OCF version tagging correctly

The OCF spec intended the version in

<resource-agent name="..." version="...">

to be used for the version of the resource agent itself, and
the version in

<version>1.0</version>

to be the version of the OCF spec the RA was written for
(which should always be 1.0 at this point).