For PersistedAliasMapper and PersistedPatternMapper, language handling
when resolving a URL route paramter was not explicit enough.
PersistedAliasMapper incorrectly resolved language default records even
when the HTTP request contained a language aspect and a more specific
record (having the same slug value) would have been available.
That was similar in PersistedPatternMapper when `uid` field was not
defined in corresponding pattern (e.g. `^(?P<title>.+)-(?P<uid>\d+)$).
For both mentioned scenarios language restrictions and fallback handling
has been integrated. Records are retrieved in the following order:
+ "all language (-1)", most specific if present, can't be localized
+ "current language" most specific for the current given request context
+ "language fallbacks" (might include "default language")