feat: rename vyper.interfaces to ethereum.ercs

[ControlCplusControlV]

What I did

Fixed Issue #3675

How I did it

Honestly I just found and replaced, and it didn't break(??). Would double check but this seems to be working to me

How to verify it

Run the tests, they seem to pass?

Commit message

Aliased vyper.interfaces import to ethereum.ercs

Description for the changelog

Aliased vyper.interfaces import to ethereum.ercs

Cute Animal Picture

This is who you're bullying when your request changes on my PR (jk ... pls do whatever is necessary)

[codecov-commenter]

Codecov Report

Attention: 1 lines in your changes are missing coverage. Please review.

Comparison is base (55e18f6) 84.78% compared to head (36dcab9) 84.80%.
Report is 3 commits behind head on master.

❗ Current head 36dcab9 differs from pull request most recent head 8434193. Consider uploading reports for the commit 8434193 to get more accurate results

Files	Patch %	Lines
vyper/semantics/analysis/module.py	66.66%	0 Missing and 1 partial ⚠️

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #3741      +/-   ##
==========================================
+ Coverage   84.78%   84.80%   +0.02%     
==========================================
  Files          92       92              
  Lines       13139    13139              
  Branches     2929     2929              
==========================================
+ Hits        11140    11143       +3     
+ Misses       1535     1532       -3     
  Partials      464      464              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[charles-cooper]

this seems fine. do we want ERC20, ERC721, etc or IERC20, IERC721, etc? @fubuloubu

[ControlCplusControlV]

ERC20, ERC721, etc. Unfortunately it seems like the masses prefer it, and it has also grown on me, although do we risk namespace collisions with other libs if the stdlib is canonically taking up ERC20?

[fubuloubu]

ERC20, ERC721, etc. Unfortunately it seems like the masses prefer it, and it has also grown on me, although do we risk namespace collisions with other libs if the stdlib is canonically taking up ERC20?

It's namespaced behind a module, so can always rename the import

[fubuloubu]

this seems fine. do we want ERC20, ERC721, etc or IERC20, IERC721, etc? @fubuloubu

As is e.g. ERC20

[charles-cooper]

thanks!