`updateRewardsClaimed()` and `rewardsClaimed()` become inaccurate once rewardsManager is out of ajna

[ith-harvey]

Description of change

High level

• removed ajna balance restriction from _transferAjnaRewards()
• applied the ajna balance restriction on the rewarded amount in a new enforceRewards() method at a lower level in the logic flow. By applying the restriction at this depth updateRewardsClaimed() and rewardsClaimed() are altered properly across all calls against the contract.
• re-applied a ajna balance check inside _calculateAndClaimAllRewards() in the event unstake() is called and the caller should receive rewards for updating exchange rates and staking rewards
• added a maxAmount_ argument to _calculateAndClaimStakingRewards() in order to ensure the amounts reduced from the rewardsClaimed() accumulator were accurate.
• SIDE EFFECT OF CHANGE: calculateRewards() now provides an accurate rewards calculation restricted by the ajna balance of the contract at the time the call is made.

Description of bug or vulnerability and solution

There is a discrepancy in the rewardsManger.sol contract's reward accumulators and events when we apply the ajna balance restriction to the amount of rewards transferred to the updaters and staking claimers.

• rewardsClaimed() - was greater than the amount claimed by caller
• updateRewardsClaimed() - was greater than the amount claimed by caller
• ClaimedRewards event - was emitting a greater value then was actually claimed

Contract size

Pre Change

## Post Change # Gas usage ## Pre Change ## Post Change

[grandizzy]

I am not sure I fully understand the problem, when it says greater than the amount claimed by caller in

rewardsClaimed() - was greater than the amount claimed by caller
updateRewardsClaimed() - was greater than the amount claimed by caller
ClaimedRewards event - was emitting a greater value then was actually claimed

you mean greater than the amount received by claimer?

[ith-harvey]

This functionality is to be expected, closing PR