Standard object convention for token pairs and shares. #90
Description
Add a standard convention for handling token pairs across the app. This should be a defined type and the same states should be used for the tokens pairs in all products.
- Trade, token1 and token2 occur as normal.
- Stake and Unstake, token1 is OCEAN and token2 is DT.
This is also needed because the unlockModal has a very messy implementation in the unstake component due to how the current states are used. This will also mean that states regarding user shares and pool information will be separate from the token1 and token2 states, and the token pair will be stored inside a shares object.