feat: adding start and end block filters to Deposits api

[AlexanderLiteplo]

Need to add these in order to update our defi llama dashboard data source.

This requests in this file:
https://github.com/DefiLlama/bridges-server/blob/master/src/adapters/across/index.ts

will be replaced with simply reading and transforming the data from this api.

In order to support the DefiLlama adapter we also need to return the FIllBlockNumber so I have added that in this PR as well.

[amateima]

Can you share more details how these query params will be used? How big will be the typical block interval? What's the expected calls frequency?

Also, given the size of the interrogated tables, I think new indexes are necessary in those 3 tables where we want to filter by block number

[AlexanderLiteplo]

Hey @amateima

For the block intervals DefiLlama uses the following:

// each chain should have number of blocks per approx. 1.5 or 2 hours. default is 400.
export const maxBlocksToQueryByChain = {
  default: 300,
  ethereum: 300,
  polygon: 1000,
  fantom: 800,
  arbitrum: 3000,
  era: 5000,
  linea: 3000,
  manta: 800,
  blast: 2000,
  avax: 3000,
  bsc: 2000,
  optimism: 3000,
  xdai: 400,
  aurora: 5400,
  celo: 1200,
  klaytn: 6000,
  sui: 2400, // sui creates a checkpoint about every 3 seconds
  solana: 6000,
  taiko: 100,
  sonic: 10000,
  base: 3000,
  arbitrum_nova: 3000,
  polygon_zkevm: 2000,
  scroll: 2000,
  mode: 2000,
  mantle: 2000,
  "b2-mainnet": 2000,
  berachain: 3000,
  hyperliquid: 3000,
} as { [chain: string]: number };

Frequency:
This query will be run hourly.

Indexes:
Great catch I'll add indexes!