Add LP staking into Picasso runtime

[RustNinja]

This PR added reward and farming pallets to cover use cases related to LP Reward staking

Introduced configuration of this pallets to picasso-runtime

Reward and farming pallet contains Mock Runtime and covered by unit tests.

• reward pallet stores stakes and claimable reward for LP stakers.
• farming pallet provides extrinsics:
  for Root origin:
  update_reward_schedule - create or overwrite the reward schedule
  remove_reward_schedule - Explicitly remove a reward schedule and transfer any remaining back to holding account
  for any origin:
  deposit - Stake the LP tokens in the reward pool and lock user balances until withdraw action(Store value in reward pallet)
  withdraw - Unstake the LP tokens from the reward pool
  claim - Withdraw any accrued rewards from the reward pool

on_initialize hook - distribute reward each N block according to scheduled(created by update_reward_schedule extrinsic). User steel need to call extrinsic claim to move reward from FarmingAccount to user account.

picasson-runtime implements two runtime function for rpc endpoints:

• compute_farming_reward
• estimate_farming_reward

conppsable-node exposes this RPC endpoints for picasso runtime.

[josietyleung]

@kollegian can we test this out please? thanks

[kollegian]

@josietyleung this is wip. Writing test plan now.

[RustNinja]

Can you try running it locally, using

nix run .#devnet-picasso-complete

and check that it works nicely?

yes. i checked.
it works fine.

i use locally:
nix run --extra-experimental-features nix-command --extra-experimental-features flakes .#devnet-picasso

there are associated pallets.
extrinsic for creating the pool and deposit/stake/claim tokens:

and
chain state

working close with @kollegian to test it together

[kollegian]

@josietyleung @blasrodri @RustNinja tested lp staking sirs. Other than one bug it seems good. #3555
The test plan can be seen here
https://docs.google.com/spreadsheets/d/19-kLAIwggsZW1WaPzDBEPi-DPeIIJCzxfXKluqsEQaE/edit#gid=585780262

[blasrodri]

This is failing here https://github.com/ComposableFi/composable/actions/runs/4881822141/jobs/8711166782#step:6:9790

[RustNinja]

@josietyleung @blasrodri @RustNinja tested lp staking sirs. Other than one bug it seems good. #3555 The test plan can be seen here https://docs.google.com/spreadsheets/d/19-kLAIwggsZW1WaPzDBEPi-DPeIIJCzxfXKluqsEQaE/edit#gid=585780262

We already discussed with @kollegian and I want to leave explanation here:
@kollegian found the issue/bug that related only to amount in event DistributeReward
here is the screen:

but actually it is not a bug. this is by design.

DistributeReward event with a high accuracy means how manny assets we distribute each block or each period.

Imagine that we want to distribute BTC(it will help us easily understand the logic if we take BTC for example). or some very expensive assets.
each block we will distribute very tiny amount of BTC that is much less then 1 satoshi. for example 0.1 Satoshi
But after 10 blocks distributed 1 satoshi.
DistributeReward event emit each block(on N period) and will show with more accuracy how many satoshi we are distributing
so in this case DistributeReward amount is 10 but actually it means 0.1 satoshi.
We are not able to reduce the accuracy for this event because then user will not see any distribution/changes in event frequently at all but there is distribution.
So we need high accuracy only in this DistributeReward to show changes for frontend in case when distribution is much smaller than 1 unit of Asset.

[RustNinja]

This is failing here https://github.com/ComposableFi/composable/actions/runs/4881822141/jobs/8711166782#step:6:9790

@blasrodri
thanks.
it is not related to this pr.
but I created another PR to fix warning/failing of CI benchmarking step for all pallets in composable repo.

#3557

Please re-approve this PR because i push changes and remove commented code.