Make sure JS Code Hints list exact matches first

[lkcampbell]

This PR fixes issue #3971.

[lkcampbell]

@dangoor, I'm not 100% sure this solution is the correct approach. Right now I am addressing the problem at the JavaScript Code Hints level. Should it be be approached at the higher level of the String Match code?

For example, here's a QuickOpen scenario. If I create files xxx.txt and XXY.txt, then enter "xx" or "XX" as my search string, I always get "xxx.txt" as my highest match and "XXY.txt" as my second choice. Is this by design? Should all String Match results be case sensitive or should it be a case by case basis?

[dangoor]

Ideally, StringMatch would have a preference for characters that match the case exactly. I think there may be an issue open on that specifically.

[lkcampbell]

In that case, disregard this PR. I want to address this in a broader scope. I will either change this or close it and submit another PR.

[lkcampbell]

@dangoor, I'm closing this PR, going to try out a different approach this week.