feat: Ext. solvers operating driver tracker

[sunce86]

Problem

Competition

• [ ] Remove /reveal endpoint completely.
• [ ] Remove uninternalized call_data field from settlement_call_data db table.
• [ ] Move populating internalized_call_data ☝️ from competition time to settlement update.
• [ ] #2718
• [x] #2719
• [ ] #2720
• [ ] #2721
• [ ] Autopilot to confirm that /solve.orders are not outside the auction - https://github.com/cowprotocol/services/pull/2712
• [ ] [Optional] #421

Postprocessing on settlement event

• [x] #2722
• [ ] Stabilize solver competition table - needed so that settlement update can fetch data from /solve response.
• [x] #2745
• [ ] Check - auction id exists and valid
• [ ] Check - competition winner settled the solution
• [ ] Check - solution settled before deadline
• [ ] Check - score can be computed and >= than competition score
• [ ] Check - solver settled all promised orders
• [ ] Check - pre/post interactions
• [ ] #2667

[fleupold]

Check on settlement update - solution settled before deadline

For this one I'd be a little careful and maybe not immediately circuit break (if you settle an auction 1h later sure, but if it's a few blocks past the deadline I'd give it a pass.

[MartinquaXD]

Just wanted to add that since there are already solvers which run their own driver we need to let them know in advance whenever we change the API between autopilot and driver. For the currently listed tasks that would be:

1. removing the score field
2. removing the /reveal endpoint

Both of these could be implemented without breaking existing drivers (just ignore the score field) but it would be good to let them know regardless.