Ensure consumers are updated for nv25 CalibrationNet upgrade

[BigLep]

Done Criteria

Lotus, Venus, and Forest are using the "expected f3 functionality" so we can have successful Calibration testing.

Why Important

Gain confidence that the "expected f3 functionality" will be in place in mainnet for nv25.

Notes

• "expected f3 functionality" includes both updating to the appropriate go-f3 version but also supporting things like Mechanism to reduce the need for two network upgrades for F3 activation to one #828
• A similar task will be created for mainnet.

Status

This may just link to subtasks in the client implementation repos.

• chore: upgrade to go-f3 v0.8.3 lotus#12941
• Venus
• chore(f3): upgrade go-f3 to 0.8.3 ChainSafe/forest#5396

[rjan90]

Unless there are late stage changes needed to be made, due to issues found during large scale testing: go-f3 v0.8.2 looks to be the latest release before the Calibration network upgrade.

• Lotus updated to go-f3 v0.8.2 here: chore: upgrade to go-f3 v0.8.2 lotus#12917
• Venus updated to go-f3 v0.8.2 here: https://github.com/filecoin-project/venus/pull/6450/files#diff-32949cfd6e9cdd3ad79705a197d75a275ad1cf2bacb6ff4547021af519b47cf8
• Forest updated to go-f3 v0.8.2 here: chore: upgrade go-f3 to v0.8.2 ChainSafe/forest#5335

[rjan90]

The go-f3 release for the nv25 Calibration network upgrade will be v0.8.3, release is expected to be published on 2025-03-13

[rjan90]

Informed Venus and Forest that v0.8.3 will be the release that will be used in the Calibration network upgrade: https://filecoinproject.slack.com/archives/C0556MSR945/p1742232052943299?thread_ts=1742231841.427349&cid=C0556MSR945