Fix supervisor: report vault execution so stuck-scan order isn't fixed

[holyfuchs]

Closes: #177

waiting for this to merge: onflow/FlowActions#139
for now testable with:
(cd lib/FlowALP/FlowActions && git checkout holyfuchs/autobalancer-callback)

Description

The supervisor “check the first N vaults” logic was fixed: vault executions are now reported to the registry, which keeps an ordered list of “least recently executed” vaults. The supervisor then scans only those first N (e.g. 5) and recovers the ones that are actually stuck, instead of always the same fixed set.

What was implemented

• Execution callback
  Each AutoBalancer now has an execution callback that runs after a scheduled rebalance. The callback calls the registry with that vault’s id so the registry can update its internal order (remove id from the list, append to the end).

• Shared callback resource
  In FlowYieldVaultsAutoBalancers, a single RegistryReportCallback resource per account implements DeFiActions.AutoBalancerExecutionCallback. Its onExecuted(balancerUUID) calls the registry so the vault that just ran is reported by id. Every new AutoBalancer gets a capability to this shared callback and passes it to setExecutionCallback(cap).

Context (from discussion)

The supervisor was limited to processing a small batch (e.g. first 5 vaults) per run. The agreed short-term approach was to order the vault list by “last executed” so the supervisor always checks the oldest / least recently executed vaults first (most likely stuck).