Updated benchmark for tesseroid

Profiling code need update for new function names
Using collections.deque for the queue

Docs say it is more efficient. Benchmark says it doesn't make much of a
difference. Still, better use it just in case.
Dont precalc distance, stop alloc in too_close

In gravmag.tesseroid:
Moved distance calculating into too_close.
Sorting input 'points' array instead of allocating a buffer and
splitting that.
too_close now returns the index that splits 'points' into don't need
division and need division.
Using sincos to calculate sin and cos at the same time.
Raise a ValueError if trying to calculate directly on top of the
tesseroid.
Check the Fatiando vs Tesseroids result

In the benchmark, just run a quick check if they are equal.
Increase accuracy of GLQ nodes