Handle question mark when fetching binary data from backend. fix #249

Fix issue #249

Tests that demonstrate the problem are in https://github.com/phpcr/phpcr-api-tests/pull/143
the problem is that we do a parse_url on the not yet encoded path. at this point, the path is not url encoded - this only happens in transport. its *not* an url at this point, its a jcr path which legally can contain `?`.

its either doing this or parsing the file location manually. not sure which is better - we would know rather precisely how the location looks: `jackalope://<sessionid>/<path>`