Cardano Updates

chore: align all Cargo workspace deps

I had an assumption that turned out wrong. `applyTick` is called just before
`applyBlock`, and I thought it's applied on each "tick" (ie. new slot).

13:59 $ cabal run ouroboros-consensus-cardano:run-threadnet -- run --threadnet-config run-threadnet-example-config/example-threadnet-config.json --slots 15 --txs-per-slot 10
...
("Node",CoreNodeId 0,"current slot",SlotNo 14,ShelleyLedgerLeiosState {sllsMaybeAnnouncedEb = Nothing, sllsTooSoonToCertify = False, sllsApplyTickCount = 2, sllsApplyBlockCount = 2})
("Node",CoreNodeId 1,"current slot",SlotNo 14,ShelleyLedgerLeiosState {sllsMaybeAnnouncedEb = Nothing, sllsTooSoonToCertify = False, sllsApplyTickCount = 2, sllsApplyBlockCount = 2})
("Node",CoreNodeId 2,"current slot",SlotNo 14,ShelleyLedgerLeiosState {sllsMaybeAnnouncedEb = Nothing, sllsTooSoonToCertify = False, sllsApplyTickCount = 2, sllsApplyBlockCount = 2})
*** Exceptions?
Nothing
*** Tips
Just (SlotNo 14,fromList [(CoreId (CoreNodeId 0),At (BlockNo 1)),(CoreId (CoreNodeId 1),At (BlockNo 1)),(CoreId (CoreNodeId 2),At (BlockNo 1))])
*** Leios
("eb-slotno",fromList [(CoreId (CoreNodeId 0),fromList []),(CoreId (CoreNodeId 1),fromList []),(CoreId (CoreNodeId 2),fromList [])])
("eb-points",fromList [(CoreId (CoreNodeId 0),fromList []),(CoreId (CoreNodeId 1),fromList []),(CoreId (CoreNodeId 2),fromList [])])
("eb-txs",fromList [(CoreId (CoreNodeId 0),0),(CoreId (CoreNodeId 1),0),(CoreId (CoreNodeId 2),0)])
*** Outputting log files

Signed-off-by: Chris Gianelloni <[email protected]>

docs: gateway fixed revision number

gateway: clarify STT header selection semantics

feat: make sure mithril package files are stable

chore: more logs

When the service worker is woken by a content script connection,
the runtime.onConnect listener was not yet registered because it
was set up lazily inside the dynamically imported modules. This
caused the first DApp connector call to fail.

Call getBackgroundMessenger synchronously before the dynamic import
so the listener is in place immediately. The singleton ensures all
later exposeApi calls reuse the same messenger instance.