Division by 0 can freeze emissions claims for veSatin holders
The function `_calculateClaim()` is responsible for the calculations of the amount of emissions a specific veSatin is entitled to claim. In doing so, this code is executed (code with mitigation from TRST-H-1):\\n```\\n    if ((lockEndTime - weekCursor) > (minLockDurationForReward)) {\\n         toDistribute +=\\n            (balanceOf * tokensPerWeek[weekCursor]) / veSupply[weekCursor];\\n    weekCursor += WEEK;\\n         }\\n```\\n\\nThe variable veSupply[weekCursor] is used as a denominator without checking if it's 0, which could make the function revert. If the protocol ever reaches a state where veSupply[weekCursor] is 0, all the claims for veSatin that were locked during that week would fail for both past and future claims. The same issue is present in the function `_calculateEmissionsClaim()`
Ensure veSupply[weekCursor] is not 0 when performing the division.
```\\n    if ((lockEndTime - weekCursor) > (minLockDurationForReward)) {\\n         toDistribute +=\\n            (balanceOf * tokensPerWeek[weekCursor]) / veSupply[weekCursor];\\n    weekCursor += WEEK;\\n         }\\n```\\n