bug: pattern matching should look for most specific rule defined

[lanorkin]

Tested with latest available version - 11.2.3

Looks like when no exact match found, tool tries to find first available pattern in simple A-Z order, while instead it should be looking for most specific redirect defined.

Steps to reproduce - create two redirects:

/oldsegment1/ => /newsegment1/
/oldsegment1/oldsegment2/ => /newsegment1/newsegment2/

then try to navigate /oldsegment1/oldsegment2/?q=test

Expected: redirected to /newsegment1/newsegment2/?q=test
Actual: redirected to /newsegment1/oldsegment2/?q=test

[lanorkin]

Actually, looking at source code, it is AZ order just occasionally:

404handler/src/Core/CustomRedirects/CustomRedirectCollection.cs

Line 84 in 6b0c6a0

using (var enumerator = _quickLookupTable.GetEnumerator())

As it uses enumeration through Dictionary<TKey, TValue>, in reality, it is random order, because order is not specified as per msdn https://docs.microsoft.com/en-us/dotnet/api/system.collections.generic.dictionary-2

For purposes of enumeration, each item in the dictionary is treated as a KeyValuePair<TKey,TValue> structure representing a value and its key. The order in which the items are returned is undefined.