Integrate proxy detection into the verification flow

[manuelwedler]

The PoC we implement in #1655 detects and resolves proxy contracts on the fly when our API is called. It would be nice from a data analysis perspective to mark contracts in our DB as proxies by already running the detection during verification. People using our parquet exports could make use of this data then. Furthermore, we could add EIP1167 contracts to our database (#1624).

The implementation resolution still needs to be done during an API call, because we are not a block explorer and cannot keep track of changed implementations. Only the implementations of EIP1167 contracts could be added to the database (but not necessary as it can be read out of the bytecode very quickly).

Needed changes

• Specify DB schema change
• Implement DB schema change
• Integrate detection into the verification process (should be in server and not in lib-sourcify)
• Allow for storing minimal proxies in the database even though they don't have source code (see Handling "Minimal Proxy Contract" pattern #1624 )
• Still run proxy resolution on the fly when the API is called
• Upgrade DB
• Migrate existing data by running proxy detection on all already verified contracts