Capitalization in search seems to throw off relevance sorting

[jillpe]

Summary

For example, if you search for "McCalla" (without quotes) across all of the collections and group by collection, the second hit was McNutt mss. More results with "McCalla" follow a non-match. I think the search got stuck after "Mc" because there was a capital C. That would also explain why there were so many results (767).
https://archives.iu.edu/catalog?utf8=%E2%9C%93&group=true&search_field=all_fields&q=McCalla

If you search for "Mccalla" or "mccalla," you only see results with the name "McCalla," with a total of 18 results.
https://archives.iu.edu/catalog?utf8=%E2%9C%93&group=true&search_field=all_fields&q=mccalla

Acceptance Criteria

• Reason for incorrect relevance sorting based on capitalization is documented and follow up tickets to fix are created

[brijmcla]

Some added context for this one--it's difficult to tell if this behavior is still happening in the Notch8 staging site since there aren't as many indexed finding aids. I can't replicate it on the Notch8 staging site, so I'm not certain that this is an issue. This is an issue on our production arclight instance.