Fix account search always returning exact match on paginated results

[Gargron]

Fix #11365

[ClearlyClaire]

Won't the first request return up to limit + 1 results, and clients would have to use that as offset, but that would skip one database result? And later down the line, the exact match could appear a second time

[Gargron]

Okay, first request should now return exactly limit results. To fix the exact match possibly re-appearing later, the account search query methods need to refactored to be composable.

[ClearlyClaire]

I think this still skips the first result of the second pagination page? Say limit is 3, with one exact match, the service would return, for the first query: the exact match and 2 other results (results 0 and 1 from SQL)

when performing a second query, the client would use an offset of 3, that would return results 3 and 4 from the SQL query, missing the second one