fix[ux]: IERC20Detailed inherits from IERC20

[AlbertoCentonze]

What I did

ERC20Detailed should inherit from ERC20.

How I did it

Given Vyper does not support inheritance I just added implements: ERC20 and copy pasted the methods from ERC20.vyi

How to verify it

Make a mock contract that implements the builtin

Commit message

Commit message for the final, squashed PR. (Optional, but reviewers will appreciate it! Please see our commit message style guide for what we would ideally like to see in a commit message.)

Description for the changelog

Cute Animal Picture

[charles-cooper]

this looks good. can you add/update tests as appropriate?

[charles-cooper]

@pcaversaccio thoughts here?

i rather like the idea of renaming IERC20Detailed to IERC20, and changing the existing IERC20 to something like IERC20Basic

[pcaversaccio]

@pcaversaccio thoughts here?

i rather like the idea of renaming IERC20Detailed to IERC20, and changing the existing IERC20 to something like IERC20Basic

No - I think IERC20 should be the base one (i.e. without metadata) and we can rename IERC20Detailed to IERC20Metadata instead. This would be also in line with e.g. OpenZeppelin here or snekmate interfaces (I also use Metadata for naming) so we can prevent further confusion like this.

I would like to note, that if we do this we might also want to do it for ERC721 as well. I provide my own interface here already but could remove it in that case :)