Consider changing the latestTimestamp to block.timestamp in the Api3ReaderProxyV1

[Siegrift]

See:

contracts/contracts/api3-server-v1/proxies/Api3ReaderProxyV1.sol

Line 128 in bed6cb3

(, timestamp) = read();

The issue with the current implementation is that many protocols implement timestamp checks the wrong way. The most notable issue is a check that timestamp is not in the future. We are guiding against this approach in the docs, but we still observe this anti-pattern in the wild.