docs: Add EIP-1167 minimal proxy section

[aefhm]

Description

Close #350 by noting full support.

[netlify]

✅ Deploy Preview for oasisprotocol-sapphire-paratime ready!

Name	Link
🔨 Latest commit	9f80464
🔍 Latest deploy log	https://app.netlify.com/sites/oasisprotocol-sapphire-paratime/deploys/66f1ff9cdc3259000754b883
😎 Deploy Preview	https://deploy-preview-410--oasisprotocol-sapphire-paratime.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[rube-de]

do we want to mention that the explorer will detect them?
or wait with it until it will also show verified?

[aefhm]

do we want to mention that the explorer will detect them?

I think this is expected behavior? Or do you mean that we should note that Explorers only detect after a proxy transaction?

or wait with it until it will also show verified?

My first thought was to call out Sapphire differences only. 🤔

[rube-de]

Ok, I thinks it's fine like this.
Initially I thought it could raise question for devs when they don't see it as proxy directly, but as the ticket for the Explorer is still open, I hope this will be fixed.

[aefhm]

Initially I thought it could raise question for devs when they don't see it as proxy directly,

I do find this to be an issue. I believe the other proxy contracts also aren't picked up correctly by the Explorer until a transaction is made. I wonder if this page or perhaps a new one is a better place for quirks with our Explorer.

but as the ticket for the Explorer is still open, I hope this will be fixed.

Agree that the Explorer UI is the best place to convey this information.

Noting the relevant Explorer issue oasisprotocol/explorer#1536.