chore: Set up logging, metrics, alerts for BadTokenMonitor

[MartinquaXD]

Background

In order to monitor and reason about the driver side bad token detection we need helpful logs and enough metrics to set up reasonable alerts for it.

Logs I would expect:

• log address of the token when it gets added to the unsupported list
• log when token leaves the unsupported list (e.g. TTL exceeded)
• log which order UIDs get filtered out due to unsupported tokens
• to make manual debugging easier it might be nice to log the involved tokens in each (non-merged) solution that failed to simulate

Metrics I would expect:

• number of currently unsupported tokens
• number of orders filtered due to unsupported tokens

Alerts I would expect:

• alert when the number of filtered orders is too high

Of course additional logs, alerts, metrics can be added if they are deemed helpful