feat: Return order execution timestamp

[squadgazzz]

Problem

Front-end wants to show the time that was spent to execute each order. More specifically, this is required in the /account/<account_address> API.

Suggested solution

Currently, there is no persistent data in the DB. timestamp from the order_events table can't be used since the table gets cleaned up periodically. Although the order_execution table contains a block number, getting its timestamp requires access to an archive RPC node, which might not be the case for some of the chains.

At first glance, the easiest way would be to introduce a new timestamp column in the order_execution table. This can be backfilled using a script with archive nodes for each chain. Maybe, Tenderly can be utilized on networks without archive node access.

Alternatives considered

To be discussed.

Acceptance criteria

/account/<account_address> returns a response with each order execution timestamp. Since the order creation timestamp is already in place, that is only a matter of the front-end team to calculate the order execution time.

[sunce86]

If we end up doing this, I would agree with this assessment:

the easiest way would be to introduce a new timestamp column in the order_execution table