tick value in entity response does not always match the siblings data

[Qsilver97]

some interesting stats about tick alignment in entity info:

1. prevSpectrumDigest as voted in tick N put into slot N
2. whenever entity data comes in, compare against a range of 1), N-1, N, N+1, N+2
3. based on assumption we would expect the match to be with slot N+1 as 1) is the prevSpectrumDigest
4. results:
   N-1 175
   N 5644
   N+1 21481
   N+2 52

So indeed N+1 wins but a surprising number matches N due to off by one reporting of entity data

Not sure the reason, but it seems that the tick number in the entity response it not obtained in the same context as the sibling merkle calculations.

[Qsilver97]

It seems this jitter is unavoidable, if so a good workaround is for the spectrum digest matched up to the tick and use the tick that matches the spectrum hash. this is what I do client side but maybe it should be done in the node itself so the wrong tick is not returned?