Deriving temporal columns from computed columns in the permuted realm

[OlivierBBB]

The current approach to implementing EIP-6780: SELFDESTRUCT only in same transaction in the spec requires the introduction of a temporal column account/HAS_CODE_FIRST_IN_TXN. This is because in order to deal with SELFDESTRUCT's moving formard we must

• log whether accounts have code at transaction start (account/HAS_CODE_FIRST_IN_TXN)
• use that information to process SELFDESTRUCT's appropriately

The natural way to fill this account/HAS_CODE_FIRST_IN_TXN column would be to compute and constrain it in the permuted realm (acp_HAS_CODE_FIRST_IN_TXN) and derive the underlying un-permuted column in the temporal realm:

1. define and constrain a column acp_HAS_CODE_FIRST_IN_TXN in the permuted realm via (fwd-fill-within
2. reverse the permutation to recover the contents of an underlying temporal column account/HAS_CODE_FIRST_IN_TXN in the account perspective