Handle Expired TWAP and not started TWAP

[anxolin]

This PR

Includes some optional blockInfo params

This params allow the poll method to use either the blockNumber or the blockTimestamp to validate the concrete Conditional Order.

Validate start time

It will check if the order started. If it haven't then we can signal we don't want to re-check until the start time

Handle Expired TWAPs

This is causing a lot of noise in the logs. Expired TWAP orders are never deleted. Now they are

Tried it in WatchTower (adapted it in cowprotocol/watch-tower#16)

Don't fail to handle errors

Handled errors should not show as errors

Not included

Left some notes for a future PR on something that will help to reduce significantly the number of checks we need to do.
It's out of scope cause is not a trivial change. It will need a model update in watch tower

[github-actions]

CLA Assistant Lite bot:
Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

---

I have read the CLA Document and I hereby sign the CLA

---

_{You can retrigger this bot by commenting recheck in this Pull Request}

[coveralls]

coverage: 72.617% (-3.8%) from 76.379% when pulling 78c24e3 on smarter-twap-indexing into 34fbd9a on main.

[socket-security]

Removed dependencies detected. Learn more about Socket for GitHub ↗︎

🚮 Removed packages: @cowprotocol/[email protected]

[mfw78]

Nice. Only some nits about assertions / typos.

[anxolin]

Merging as this is already too big. Lets keep iterating