Incorporate and finalize the proxy format to the APIv2 response

[kuzdogan]

Following the PoC and what we learn at #1655, we should add the proxy info accordingly to the new APIv2. These related fields and their format is to be defined.

[manuelwedler]

For the GET /contract endpoint of APIv2, I propose to gather all proxy related information under a propery proxyData for being able to filter via ?fields=proxyData.

I would follow the approach of #1655, and include the following fields:

• Proxy contract:

  {
     ...
     "proxyData": {
        "isProxy": true,
        "proxyType": "EIP1967Proxy",
        "implementations": [
            {
               address: "0x751D7C0Cf91a9b7704541b44E5fF7BeC3D2caA6F",
               name: "Logic contract"
            }
         ]
     }
  }
  

• Non-proxy contract:

  {
     ...
     "proxyData": {
        "isProxy": false,
        "proxyType": null,
        "implementations": []
     }
  }
  

• Resolution error:

  {
     ...
     "proxyData": {
        "proxyResolutionError": "RPC failed"
     }
  }
  

[kuzdogan]

Sounds good to me, thank you. I tend to change the proxyData name but I don't have a good candidate. Not a blocker and just a small thing.

[manuelwedler]

Added the proxy format to the Stoplight API design: https://sourcify.stoplight.io/docs/sourcify-apiv2/branches/main/cqx62aqefyrje-get-verified-contract

I renamed the proxyData field to proxyResolution.