SPIKE: ABI Updates about fio

[ericbutz]

Adam A - Dapix, [22.04.20 10:08]
The fix contains actions used by fio.treasury, a missing action in fio.address.
The domain expiration was uint32 in the abi but the struct defines a uint64. Need input on the expected fallout from setting a new abi with this change.
EOSUSA Michael, [22.04.20 10:13]
from they hyperion side, weve got hard coded abis applying to a predefined range, since updating the abi does nothing for all the old actions before it ultimately. but once we know the block it was updated, we can cap the abi bypass range and it will properly use the hardcoded abi up to this new abi, then use the fixed one from that point forward (and any other changes pushed to it down the road)

[ericbutz]

Moved to a future release focused on eosio 2.0 upgrade. Closing.