ExactFirst doesn't work in quicksearch (maybe)

On trying to write a test to 'lock in' the bit of code that causes getquick results to be sorted by whether an exact match on first name exists if the setting includeOrderByClause is disabled ... I found out it didn't actually how I thought it should.

I was trying to lock in existing behaviour but I have some doubts about what is correct.

What is needed at this point is someone to run a critical eye over the tests I wrote starting at https://github.com/civicrm/civicrm-core/pull/6570/files#diff-9c835e782d44803ff1cacf9aea2bbfa5R2149 & confirm the behaviour being locked in is correct. The test data for the tests is at the end of the test class - ie https://github.com/civicrm/civicrm-core/pull/6570/files#diff-9c835e782d44803ff1cacf9aea2bbfa5R2393