Improve error handling on getTradeableOrderWithSignature CALL simulation

[anxolin]

Most of the erros happen during getTradeableOrderWithSignature CALL simulation.

There's many things that can go wrong here.

This error tries to make it more explicit the error handling, so it signals igiven the error, we should re-attempt later. Also, if this is expected or just an un-expeted errors.

Expected errors won't lead to the TENDERLY action to fail.
Un-expected will.

If the error handler decides that we shouldn't re-attempt later (its a final error), then it will signal that the order should be deleted.

Special mention

I changed slightly the implementation, @mfw78 pls double check if it makes sense now.

Before, we were deleting the order in case of unforeseen or un-recognised errors. This could be for example because of a temporal network failure or rate limiting or sth, so we should definitely re-attempt later.

see https://github.com/cowprotocol/composable-cow/pull/46/files#diff-8e2dc90f4a6ebdf01f8603707f37f7794972fdf1827102bfce89497804f72837R398

Edit

Analysing this case, i changed this PR to make less noise when

This order was created, and there was an AUTH, but it was revoked after doing a cancelation.

Its fine to delete the order, and I don't think we should make so much noise in these cases: 33e80fa

[mfw78]

Approve with a suggestion of how one can filter the contracts to remove those that don't comply (ie. don't implement getTradeableOrderWithSignature).

The base branch was changed.

[anxolin]

Addressed the comments and merging.

Pls let me know if you need to re-iterate again, i will follow up in another PR.