chore(shed): update trace-finding in lotus-shed miner fees & fees-inspect with a better top-down filter

[Copilot]

This PR implements a better top-down filtering approach for trace-finding in the lotus-shed miner fees and lotus-shed miner fees-inspect commands, as requested in the issue.

Problem

Previously, both commands used a bottom-up filtering approach that would trace any execution involving the target miner address. This resulted in noisy output with many irrelevant traces that didn't follow the actual cron execution flow.

Solution

The new implementation adds hierarchical trace filtering that follows the expected cron execution flow:

• Depth 0: SystemActorAddr (f00) → CronActorAddr (f03) method 2 (EpochTick)
• Depth 1: CronActorAddr (f03) → StoragePowerActorAddr (f04) method 5 (OnEpochTickEnd)
• Depth 2+: StoragePowerActorAddr (f04) → miner actors method 12 (OnDeferredCronEvent), plus any miner-related calls

This matches the actual protocol flow described in the issue:

f00->f03[2]:0                         # System calls Cron EpochTick
    f03->f04[5]:0                     # Cron calls Power OnEpochTickEnd
        f04->f02[3]:0                 # Power calls Reward ThisEpochReward
        f04->f01083949[12]:0          # Power calls Miner OnDeferredCronEvent
            f01083949->f099[0]:...    # Miner pays fees to burn address
            f01083949->f04[4]:0       # Miner reports back to Power
        f04->f02[4]:0                 # Power calls Reward again
    f03->f05[9]:0                     # Cron calls Market actor

Changes Made

1. Updated printExec function in the fees command with depth-based filtering logic
2. Updated traceBurns function in the fees-inspect command with the same filtering approach
3. Preserved existing behavior for deeper trace levels (depth >= 2) where miner interactions occur
4. Added comprehensive filtering for shallow depths (0 and 1) to focus on the cron execution path

Benefits

• Cleaner output: Filters out unrelated execution traces that don't follow the cron flow
• Faster processing: Skips irrelevant trace branches early in the recursion
• Better debugging: Highlights the actual execution path that leads to fee payments
• Protocol consistency: Matches the designed cron execution flow

Testing

• Validated actor addresses match expected values (f00=System, f03=Cron, f04=Power)
• Verified method numbers correspond to expected calls (2=EpochTick, 5=OnEpochTickEnd, 12=OnDeferredCronEvent)
• Tested filtering logic with various valid/invalid trace scenarios
• Confirmed code compiles and follows existing style patterns

Fixes #13203.

Warning

Firewall rules blocked me from connecting to one or more addresses

I tried to connect to the following addresses, but was blocked by firewall rules:

• https://api.github.com/repos/filecoin-project/filecoin-ffi/releases/tags/v1.33.1-dev
  • Triggering command: curl --retry 3 --location REDACTED (http block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to my firewall allow list

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

[github-actions]

Please update the PR title to match https://github.com/filecoin-project/lotus/blob/master/CONTRIBUTING.md#pr-title-conventions

[rvagg]

lovely

PR title now matches the required format.