Technical behind-the-scenes view for developers

### **What problem are you trying to solve?**
Sharing technical details and serving developers curiosity on how MetaMask works. This is a devmode-only feature IDEA, (when we have devmode)

Potential impact of this offering:

- Gain more trust from developers (who aren't part of our community yet), by making our transparent code base even more accessible.
- Education / answering technical users' questions in-context could be an incentive for them to choose MetaMask over other similar offerings.
- Could help increase visibility and awareness of new standards and dev resources we release.

### **Describe the solution you'd like**
Overall, a solution could be to give some in-context help in a tool-tip when devmode is on, and link it to relevant dev documentation.

Specifics:

- When devmode is on, developers get the option to "inspect" MetaMask integration elements they see on dapps (this might become increasingly interesting once we release Sneh's button, and capabilities system).
- They also can view (perhaps in a tool tip), how MetaMask is doing actions like "Tx Speed-up / Cancel", "Signatures", Storing private keys, Infura calls, Nonce.
- This goes more towards other dev features documented in Github (for learning, coding, testing, debugging): visualizing smart contract function calls could be great (overlaps with Alethio integration), advanced debugging window.

### **Additional context**
While interviewing / testing with users, I've heard the developers / technical background folks think-out-loud "Oh! I wonder how you do that technically?" "How is this done securely?" "I didn't know Connect request was implemented, this is great, when did you release it?"

In the dapp builder survey, results till date (total responses 32) show high responses on: make MetaMask easier to use for developers (14 / 32), tools for debugging (16 / 32), block explorer functionality (9 / 32)

No files, tests, or entry points are identified. Start by defining the devmode scope and choosing one focused capability, such as inspecting dapp integration elements or explaining transaction actions; done means a specific in-context view is implemented and linked developer documentation is identified.

Written by the indexing model from the issue text.