fix(ci): disable F3 on lotus until a new lotus image with calibnet F3 initial power table is published

[hanabi1224]

Summary of changes

Lotus cannot bootstrap F3 until initial power table is set. Disable F3 on lotus for now to unblock CI.

https://github.com/ChainSafe/forest/actions/runs/21977918338/job/63495549964?pr=6597#step:6:1501

ERROR: initializing node: starting node: failed to open certstore: getting initial power table: failed to load the F3 bootstrap power table and none is specified in the manifest; could not close datastore: leveldb: closed

Changes introduced in this pull request:

Reference issue to close (if applicable)

Closes#6595

Other information and links

Change checklist

• I have performed a self-review of my own code,
• I have made corresponding changes to the documentation. All new code adheres to the team's documentation standards,
• I have added tests that prove my fix is effective or that my feature works (if possible),
• I have made sure the CHANGELOG is up-to-date. All user-facing changes should be reflected in this document.

Outside contributions

• I have read and agree to the CONTRIBUTING document.
• I have read and agree to the AI Policy document. I understand that failure to comply with the guidelines will lead to rejection of the pull request.

Summary by CodeRabbit

• Chores
  • Updated test environment configurations to disable the F3 subsystem across multiple test services.
  • Updated test filter list to exclude F3-related tests from the test suite.

[coderabbitai]

Walkthrough

The PR disables the F3 subsystem in Lotus containers used for testing by adding environment variables to two docker-compose configuration files and filters out F3-related RPC parity tests. These are configuration and test filtering changes without modifications to core logic or runtime behavior.

Changes

Cohort / File(s)	Summary
Docker Compose Configuration scripts/tests/api_compare/docker-compose.yml, scripts/tests/bootstrapper/docker-compose-lotus.yml	Added LOTUS_DISABLE_F3_SUBSYSTEM=1 environment variable to disable the F3 subsystem in Lotus service containers.
Test Filtering scripts/tests/api_compare/filter-list	Added filter entry !Filecoin.F3 with accompanying comment to exclude F3-related tests from the RPC parity test suite.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• fix(f3): reset F3 on calibnet #6414: Coordinates with main PR to disable F3 subsystem across test manifests and configurations.
• fix: ignore F3 in RPC checks until reset #6547: Directly modifies the same scripts/tests/api_compare/filter-list file to add explicit F3 test filtering.
• test: add lotus-gateway parity test #6570: Adjusts api_compare test orchestration and F3 subsystem handling in docker-compose and filter configurations.

Suggested reviewers

• LesnyRumcajs
• sudo-shashank

🚥 Pre-merge checks | ✅ 6

✅ Passed checks (6 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: disabling F3 on lotus in CI until a new lotus image is published.
Linked Issues check	✅ Passed	The PR addresses the CI failure in #6595 by disabling F3 subsystem on lotus in docker-compose configurations and test filters.
Out of Scope Changes check	✅ Passed	All changes are scoped to disabling F3 subsystem in CI configurations and test filters, directly addressing the CI breakage issue.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Merge Conflict Detection	✅ Passed	✅ No merge conflicts detected when merging into main

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch hm/disable-bootstrap-checks-lotus

---

No actionable comments were generated in the recent review. 🎉

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}