Multibyte PagePath (URL) support

[tao-s]

concrete5 Japan team is taking a look at multibyte issues now.

Multibyte URL is very important to us
Therefore, we have made the pull request to meet the followings:

1. Sanitization.

We can use Japanese (and other multibyte characters) for URL slug, but there is no sanitization on both way (enter and output). What's your plan in the future?

1. Decode page path

We need to decode the page path URL at Request class in order to be able to use multibyte characters. Otherwise, it would return 404. Can we do it?

1. When printing out the page path in , we need to encode the page path.
2. Are you still planning to use PagePath object when handling Page object? Or getCollectionPath() would be obsolete?

[katzueno]

Ping.

[aembler]

I have merged this pull request with some tweaks:

1. I have included the decoding of getPath() - this fixes the 404s.
2. I have included the getEncodePath() method in the Page class3
3. I have not wrapped getCollectionPath in this method, or the other method. I feel like wrapping getCollectionPath() in this method all the time is a bad idea – it should be wrapped only on those rare times when we actually display it. Right? Thoughts?