fix: make block query cutoff properly configurable

[dylanlott]

fix: make block query cutoff properly configurable

At some point in the past, the block query cutoff configuration value was removed and a hard-coded value was added in.

This PR adds the block query cutoff back into the config and uses the config value in the calculate_deadline​ function.

Builder example environment documentation needs to be updated to reflect this change.

[dylanlott]

• wip: debug logging #183
• fix: make block query cutoff properly configurable #181 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[Evalir]

Actually, disregard the other review. This should be called BLOCK_QUERY_CUTOFF_BUFFER

[prestwich]

seconds is not enough resolution. needs to be milliseconds

[Evalir]

I wonder if it's better to explicitly circuit break the building process altogether if the deadline ends up being too close to Instant::now() instead of this being implicit, because it indicates we've ran out of time anyway.

[prestwich]

if we're trying to improve resultion, we need to add to the current timestamp in unix milliseconds. using seconds here gives us all the rounding problems we already had

[prestwich]

converting to draft until the duration math is removed and the bin-base changes are in