Empty query results when using bypass channel cache

buildChannelsQuery doesn't check for boundary condition when incrementing endSeq to provide inclusive endSeq handling.  This results in empty query results when callers are providing MaxUint64 as endseq.  The bypass channel cache is the only caller that uses this endseq value.

The bypass channel cache is only used in 2.8.x when cache compaction can't keep up with the rate of new channels being queried, so this shouldn't be hit by most users.  The `chan_cache_bypass_count` stat can be used to see whether the bypass cache has been used.

This is fixed in Lithium as part of CBG-1695.