Feature/Add product management function setProducts()

[0xdewy]

Context

closes #334
closes #329
closes #328

Changes proposed in this pull request

334 - Add ability for manager to add/remove/edit products in the staking pool by creating a setProducts(ProductParams[] products) function that lets the manager add/remove or edit existing products. The product must exist in the Cover contract to be added.
329 - Enforce max 20x leverage. The staking pool has a global variable targetWeight that must be below 20x.
328 - setProducts() allows managers to adjust any product in one tx

This PR adds a setProducts() function that allows managers to add, edit or remove products from their staking pool. The staking pool can offer full capacity for up to 20 products. This is managed by keeping track of a totalTargetWeight and a totalEffectiveWeight. Allocation for a product cannot exceed that products target weight. When setting targetWeight, the totalTargetWeight and the totalEffectiveWeight cannot exceed 20x. This means if the stakingpool is at full allocation, the manager will not be able to add another product even if they reduce the targetWeight of other products.

totalEffectiveWeight is the sum of max(product.targetWeight, product.allocatedWeight).

totalTargetWeight is the max amount the contract will allocate....can never be above 2000 (20.00)

_setInitialProducts()

• Sets all initial parameters and only checks totalTargetWeight as the pool should have no allocations yet

setProducts()

• Cannot add deprecated or non existing products
• Must evaluate current allocations if manager wants to change target weight of any products
• Can edit prices and avoid evaluating current allocations
• For targetWeight to increase on a product, there must be available capacity, even if totalTargetWeight is still below the max.

cover.getCapacityRatios()

• Added this view function in cover for when current allocations need to be evaluated in setProducts().

Note: There was some fixes made to activeStake/totalCapacities as totalCapacities was being stored/retrieved with 12 extra decimal places relative to allocatedCapacities

Test plan

Added unit tests at: test/unit/StakingPool/setProducts.js

Checklist

• Rebased the base branch
• Attached corresponding Github issue
• Prefixed the name with the type of change (i.e. feat, chore, test)
• Performed a self-review of my own code
• Followed the style guidelines of this project
• Made corresponding changes to the documentation
• Didn't generate new warnings
• Didn't generate failures on existing tests
• Added tests that prove my fix is effective or that my feature works

Review

When reviewing a PR, please indicate intention in comments using the following emojis:

• 🍰 = Nice to have but not essential.
• 💡 = Suggestion or a comment based on personal opinion
• 🔨 = I believe this should be changed.
• 🤔 = I don’t understand something, do you mind giving me more context?
• 🚀 = Feedback

[danoctavian]

A meta discussion about solving 3 issues in 1 PR

I've been doing 1 issue per PR, should we be more strict with that or just leave it to reasonable judgement case by case

[roxdanila]

A meta discussion about solving 3 issues in 1 PR

I've been doing 1 issue per PR, should we be more strict with that or just leave it to reasonable judgement case by case

I ended up merging the 3 issues into one, as they were too interdependent. So overall it does follow the 1 issue - 1 pr structure.

[shark0der]

🚀