Add `mkPlutusTxInfoFromResult` and `toPlutusTxInfoForPurpose` helpers to aid in using this nested complexity.
`validateOutsideForecast`, `validateOutputTooBigUTxO`
- Add EraForecast and ShelleyEraForecast typeclasses. - Add Timeline to distinguish between current and future forecasts. Disallow coercion between them in ShelleyForecast. - Add currentForecast and futureForecast, type-restricted to the corresponding Timeline. - Migrate test-suite to use these inplace of GetLedgerView.
We do should *not* provide a default implementation for 'fromPlutusData' because types should always be invertible from 'PlutusData'. Therefore, we force the user to make a conscious decision to not provide an implementation for this function.
The `Show` instance for Mismatch was modified to show type level information.
The same thing needs to be done for the `TreeDiff` instance.
Example of the `Expr`:
```
ghci> toExpr (Mismatch @RelEQ (42 :: Int) 100)
Rec "Mismatch (RelEQ)" (fromList [("supplied",App "42" []),("expected",App "100" [])])
```
`validateInputSetEmptyUTxO`, `validateBadInputsUTxO`, `validateMaxTxSizeUTxO`, `validateOutputBootAddrAttrsTooBig``
since the fixup is not implemented, and they correctly fail the checks in rules