would rather not reuse `:no_count` for this ignoring-the-limit feature -- seems non-obvious that asking for no count means the routine will return all results.

The reason for adding `:no_count` was for cases where you wanted to return all results right?  So maybe instead of `:no_count` we want this option to be called `:return_all` or `:no_limit`.  In these cases we don't need a separate query for the count (the caller can just count the length of the returned array).  In all other cases we need to know the number of matches (so we can make additional calls).

Actually, maybe the limiting of the number of matches to a max of 10 doesn't belong at this level, but maybe instead at a handler that is using this routine to return users to some human/machine caller?  Because other parts of accounts could use `SearchRoutines` to just find a bunch of users to iterate through and do stuff to?