Make updating the delegation state part of the chain tick function

[edsko]

The ledger specs provide the facility for validating a block extending a chain. However, as a leader we have to consider how to validate a block that we are producing. We should have an additional invariant here:

• If we produce a block with valid contents, and that block is a valid extension of the chain according to the protocol, then that block should itself be valid.
  A block is validated according to the "current" chain state, which is the chain state of the last block to be applied. However, during block validation we first process the header of that block, which includes making updates which are driven only by time. So if time has moved on, it's possible that payload contents which looked valid are no longer so, violating our invariant.

To get around this, we should require of the ledger that it exposes a "chain tick" transition, driven only by slot number, that covers all time/slot based updates to the chain state.

For Byron, this involves splitting the DELEG transitions to move ADELEGS (delegation activation) and EPOCH into a new TICK rule which takes only slot as signal, updating both delegation state and update state.

For Shelley, this involves modifying the BHEAD rule to either (a) move the header checks up to CHAIN, and rename as TICK, or (b) add a new rule TICK below BHEAD which applies the slot-driven transitions.

[mgajda]

#1052 made the leftover ticket Byron-only.

[mgajda]

So Byron part is supposed to remove dotted links here, and add dashed links, and new STS TICK.
Also it TICK will call TRC, not just initial IRC transitions for ADELEGS.

Or should we also call update STS?

Will submit it this week.

[JaredCorduan]

the chain tick functionality is now exposed in cardano-ledger. but the rules are not adapted. I am going to de-prioritize this issue for now.

[JaredCorduan]

Development of Byron code has been frozen and only potential security fixes will be applied in the future