[Tech Task] Implement info subsection for request provenance, contract petname and method name #23945
Description
Important
@SayaGT to provide tooltip wireframes and copy
Progresses #23905
Context
The first subcomponent for the "info" sections of redesigned transaction confirmations we'll implement is the following:
Approach
Create a dedicated component inside the confirm/info folder. The component will be imported inside the contract-interaction info component.
This component will make use of the existing <Name /> PetNames component.
It will also leverage https://www.4byte.directory/ to get the method name in human-readable format. This can be done by using getContractMethodData such as it's already used here. Note this method already takes into account whether or not that 3rd party request has been authorized by the user (so we will test both scenarios later on).
Acceptance Criteria
- Implement the 3 fields "Request from", "Interacting with" and "Method" as a new component.
- Import that component on the contract interaction info component.
References
https://github.com/MetaMask/MetaMask-planning/issues/873
#20098