in apiParser, expectedObject allow for 'or' notation

[gardenofwine]

a result from the server can return a complex json structure which can have different set of fields for each separate request. The validateObject function in utils.js doesn't know how to cope with a situation like that.

An example is the bill api.
This bill request:
http://www.oknesset.org/api/bill/7171/?callback=Ext.util.JSONP.callback
is a gov_proposa and not a knesset_proposal, so the validateObject function returns:
"bill not valid. Failed match for 'proposals'. Failed match for 'knesset_proposal'. Failed match for 'explanation'. Failed match for undefined. object of type 'undefined' doesn't match any of the expected types 'string'"