Use preview functions for precise accounting

[trmid]

Summary

convertToAssets and convertToShares are not guaranteed to use current onchain conditions to calculate conversions and may use some approximation to return more of an "average" prize. Yield vaults that implement these as average price oracles may behave poorly with the prize vault when these functions are used for precise accounting functions.

To address this, usage of these functions have been replaced with the yield vault preview functions instead to provide precise accounting based on current onchain conditions. However, this comes with new challenges since these preview functions may revert in some scenarios, but must be used in the prize vault's maxDeposit, maxWithdraw, etc. functions, which MUST not revert. The following changes have been made to allow the usage of these preview functions:

• New function added: totalPreciseAssets() (returns the total assets using current rates from the yield vault previewRedeem function)
• New function added: _tryGetTotalPreciseAssets() (Attempts to fetch the totalPreciseAssets, but catches any reversions and indicates that the call was unsuccessful. This function is used in the maxDeposit, maxWithdraw, etc. functions so they can return zero instead of reverting)
• totalAssets() is no longer used for any accounting functions besides convertToAssets and convertToShares, since all three of these functions are treated as "approximations" by the spec.

[linear]

GEN-1238 [336/337/64] Use preview functions for precise accounting

[github-actions]

LCOV of commit 48999e1 during coverage #518

Summary coverage rate:
  lines......: 99.5% (213 of 214 lines)
  functions..: 100.0% (59 of 59 functions)
  branches...: no data found

Files changed coverage rate:
                              |Lines       |Functions  |Branches    
  Filename                    |Rate     Num|Rate    Num|Rate     Num
  ==================================================================
  src/PrizeVault.sol          |99.5%    184| 100%    48|    -      0

[asselstine]

The revert suppression is unfortunately, but the logic makes sense to me