URI created by TextReader stored in a documents DocumentMetaAnnotation is invalid when path contains whitespaces about dkpro-core-asl HOT 3 CLOSED

I've created a small unit test to reproduce the problem and can confirm it. 
Currently the ResourceCollectionReaderBase class stores the original location 
in the documentUri field. The issue can be fixed by storing the resolved URI in 
the documentUri field and the resolved base URI in the baseUri field. I believe 
that change does not break things for the users. However, the documentUri may 
become quite different from the location passed into the TextReader. Possibly 
there is another solution so that the documentUri still bears some resemblance 
to the original location.

Thinking about it, I believe it would be best not to insist on using the 
original location as part of the documentUri, because that may lead to multiple 
documents having the same documentUri. E.g. when resolving files from the 
classpath, multiple files may be at the same classpath: location, but each one 
will resolve to a separare jar: location.

- Using resolved URI and resolved base URI to fill document metadata fields
- Added TextReader test case with space characters in path
---
rev 204