climb_anti_bhop on low duration does not fully prevent perfs

[zer0k-z]

It is still possible to bhop off low delay antibhop triggers. This happens because the api triggers use server tickcount instead of client tickcount.
With a 1 tick antibhop trigger for instance, it is possible that the player can still perf after 2 server ticks because of packet delays.

Generally for player movement we should avoid using server tick if possible, as movement is processed during client's user command and dosen't depend on server's ticking.