Deployment artifacts preparation

[cygnusv]

When contracts are deployed, information about the deployment such as addresses and ABIs are stored in the build/deployments directory (see https://eth-brownie.readthedocs.io/en/stable/build-folder.html#the-build-folder).

For release purposes, we want this information to be structured in a more amenable way, potentially similar to how we're already doing manually, which is as individual JSON files on the artifacts directory (this is useful for when our repo is published as an NPM package and consumed by others). There are many open questions/tasks here:

• Decide on a structure to organize deployment artifacts (e.g., under the artifacts directory)
• Create tooling that automatically organizes deployment data generated by Brownie into the artifacts structure that we decide
• How to deal with our multichain setting? Most contracts are on Ethereum, but some contracts will start to live on Matic. How about non-EVM compatible networks (e.g. Polkadot, Solana, etc)?

We can consider this as a meta-issue that will probably branch out to new more concrete issues

[theref]

do we want to use the built in release functionality provided by github? similar to nucypher/

we can dump all json/abi etc into the artifacts directory and then tag it

[cygnusv]

Latest ideas @KPrasch and I just discussed:

• Extend ape deployment scripts to obtain the newly deployed addresses and ABIs and track these internally somehow (TBD, potentially a simple JSON file that's written locally)
• Create a script that process the JSON file and produces:
  • a new nucypher-style registry
  • a new NPM package

[KPrasch]

Closed by #119