improvement: market aid structure and deployement

[denverbaumgartner]

today: the market aid class is initialized from a contract address that is passed in by the user. because the factory can tie a user's signing address to all of the market aid instances that it controls, it would be nice if in the setup we had the option for a user to either select a market-aid instance that they would like to deploy to, or to create a new one.

soon: we should improve rubi/rubi/contracts/aid.py, and the repo as a whole, to include something like the following:

• [] incorporate aid contracts in the factory class for easy access upon initialization
• [] if a user does not have a market aid contract, we should have an easy integration function that deploys one and gives the necessary approvals to it
• [] as a whole, we should drastically improve the tooling support we provide around market aid. gas costs is a crucial thought here with a subgraph solution that is soon to be open-sourced in mind

[denverbaumgartner]

work towards this end has been continued with the open-sourcing of a new subgraph repo, rubi-subgraphs. 🔜 i hope to add in historical data support from these subgraphs along with some work i have done on quantifying historical gas spend.