[HOLD] only use first initial in name queries when not ambiguous or no alternate identities

[peetucket]

HOLD - may want to figure out how to do some comparison tests between both styles of queries for some subset of authors to see what the impact is

For people whose first initial and last name combo is ambiguous within Stanford, it is dangerous to use this combination with an OR in the name query as it will result in lots of false positives for those people. The solution was to stop using first initial only variants when searching (i.e. setting Settings.HARVESTER.USE_FIRST_INITIAL to false), but this has the downside of missing some legitimate publications where something was published using only the first initial and not the full first name.

This PR allows most name queries to execute with a first initial search variant to maximize results, unless we can determine

• there actually is an ambiguity problem with first initials in our database of names OR
• there are non-Stanford alternate identities (which means there could be name ambiguities at the other institution, which is also problematic)

Note that we currently keep authors who have left Stanford in our database and make them inactive - and thus even after someone has left Stanford, we still are not going to include the first initial query on the remaining authors at Stanford. This is desirable, otherwise an author with an ambiguous first initial that leaves Stanford would potentially cause many new false positives to appear for other authors with the same last name and first initial.

But it has some potential issues:

• it causes the search behavior to not be consistent from author to author, which can cause coverage for some authors to better than authors (but at least its not equally worse for all)
• this behavior may change for a given author depending on who else is at Stanford and can change over time
• any change to queries runs the risk of unintential side effects (e.g. some additional false positivies being returned in an unexpected way)
  A more consistent solution is to have users add first initial variant into their alternate names if needed, though this requires user action and is unlikely to happen at scale.

This approach needs to be validated with the Profiles team.

[peetucket]

this configuration parameter is no longer needed since we will now selectively decide if we want to use the first initial or not

[jmartin-sul]

one refactoring suggestion, and one bit of logic that i'm not sure is working as expected, but otherwise LGTM

[jmartin-sul]

re-reviewed, approved, but leaving unmerged due to testing concern outlined in description