Broken FileResultCoder via parseSchema change

Recently this commit

https://github.com/apache/beam/commit/3fff58c21f94415f3397e185377e36d3df662384

introduced more strict schema parsing which is breaking the contract between FileResultCoder and FileSystems.matchNewResource().

Coder takes ResourceId and serialize it via `toString` methods and then relies on filesystem being able to parse it back again. Having strict scheme:// breaks this at least for Hadoop filesystem which use URI for ResourceId and produce toString() in form of `hdfs:/some/path`

I guess the ResourceIdCoder is suffering the same problem.