Go to File Search Should Not Prioritize Alphabetical "Fuzzy" Match Over Exact Match in Results

### Description

When using the Go to File search the results appear to be sorted alphabetically which means the default selection is commonly not what the user is looking for.

For example:
In the below screenshot I search for "DirectionalMovementOfIndicatorTest" and in the results, the default selection is a "fuzzy" match despite the exact match was also found.


It would be nice if there's an exact match it's placed first and selected by default. The fuzzy matches can then come after, sorted via the existing criteria.

### How to reproduce

1. In a new or existing project create three new class files, all named similarly. For example:

DirectionalMovementDownOfIndicatorTest.java
DirectionalMovementOfIndicatorTest.java
DirectionalMovementUpOfIndicatorTest.java

2. Open the "Go to File" search (alt+shift+o on Windows)
3. Search for a file which name is not the first in natural sorting order (i.e. DirectionalMovementOfIndicatorTest.java)
4. Press ENTER as soon as the search results pop up cause you're in the zone
5. Notice with chagrin that you are not where you expected to be. Level of confusion correlated with how similar the classes are.

### Use case/motivation

This is low priority but if a UX uplift initiative ever gets going this should be included.

### Related issues

_No response_

### Are you willing to submit a pull request?

No

### Code of Conduct

Yes

Start by reproducing the Go to File search with the three similarly named Java files described in the issue, then locate the search implementation; no source file or test is named. Done means an exact filename is ranked first and selected by default, while fuzzy matches retain the existing ordering afterward.

Written by the indexing model from the issue text.