Support "old" and "new" JSON options format

Example of 1.1 format:

[ {name:"Acme Release 38166-0",value:"38166"}, {name:"Acme Release 38132-0",value:"38132"}, {name:"Acme Release 38079-0",value:"38079"}, {name:"Acme Release 37881-0",value:"37881"}, ]

Example of "old" format

{
"Zsecurity[STAGE]":"NEEDSTAGEARRAY",
}

I assume for the JSON option format, you mean to support the Ctlcenter format?

http://doc36.controltier.org/wiki/Job-v20.xml#valuesUrl_JSON

vs

http://rundeck.org/1.0/RunDeck-Guide.html#json-format

which is the same as

http://rundeck.org/1.2/RunDeck-Guide.html#json-format

i think the old method also sorted the keys...otherwise the order would be nondeterministic. Going to sort them unless someone votes otherwise.

(from [84e9d008255014234db5f8899482bdd24554aa05]) Document support for old json options format [#291 Support "old" and "new" JSON options format ] https://github.com/dtolabs/rundeck/commit/84e9d008255014234db5f8899...