All information that is necessary from the ledger to construct Plutus' TxInfo.

This is the helper type that captures translation of Tx to PlutusTxInfo.

It is important to note that TxInfo is always the same per Plutus version for each Tx. This invariant allows us to avoid duplicate computation by memoizing all possible PlutusTxInfos per transaction. Starting with Dijkstra era there is a slight complication introduced to this invariant where top level transaction has a different PlutusTxInfo for Guarding purpose, when compared to all other purposes. That is the reason why result is somewhat strange, namely a function from PlutusPurpose to PlutusTxInfo. It is also done this way, instead of adding ScriptPurpose as an argument to toPlutusTxInfo to preserve capability of memoization, hence nested Either

Given the prepared PlutusTxInfoResult and the purpose this function allows constructing the PlutusTxInfo, while memoizing the computation from PlutusTxInfoResult for its subsequent uses.

This is what toPlutusTxInfo would be without the intermediate PlutusTxInfoResult.

Note - Using this function totally drops any memoization of TxInfo, as such use it only for testing or tooling that doesn't care about performance.

Helper function to use when implementing lookupTxInfoResult for plutus languages that are not supported by the era.

This is just like mkPlutusScript, except it is guaranteed to be total through the enforcement of support by the type system and EraPlutusTxInfo type class instances for supported plutus versions.

This is just like mkBinaryPlutusScript, except it is guaranteed to be total through the enforcement of support by the type system and EraPlutusTxInfo type class instances (via calling `mkSupportedPlutusScript) for supported plutus versions.