feat: add env-var to disable F3 activation

[rjan90]

Related Issues

filecoin-project/go-f3#732

Proposed Changes

Adds a new environment variable LOTUS_DISABLE_F3_ACTIVATION that allows disabling F3 activation for a specific contract address or epoch.

Format: contract:address or epoch:number

Checklist

Before you mark the PR ready for review, please make sure that:

• Commits have a clear commit message.
• PR title conforms with contribution conventions
• Update CHANGELOG.md or signal that this change does not need it per contribution conventions
• New features have usage guidelines and / or documentation updates in
  • Lotus Documentation
  • Discussion Tutorials
• Tests exist for new functionality or change in behavior
• CI is green

[Kubuxu]

The checks should be applied in NewManifestProvider and totally disable the manifest providers. So the contract disable would disable the contract manifest provider, and epoch would disable the static manifest provider.

[rjan90]

Thanks! I have removed the the check in fetchManifest, and added the check to NewManifestProvider and:

• Completely disable the contract manifest provider if the contract address matches
• Completely disables the static manifest provider if the bootstrap epoch matches

[rjan90]

@Kubuxu Wondering if it is worth changing the LOTUS_DISABLE_F3 environment variable here, so it is a clearer distinction between all of them?

• LOTUS_DISABLE_F3_PASSIVE_TESTING = disables passive testing
• LOTUS_DISABLE_F3_ACTIVATION = disable the F3 activation, either by contract or epoch
• Rename LOTUS_DISABLE_F3 --> LOTUS_DISABLE_F3_ACTIVE_NETWORK = disables a already active/running F3 network.

[rjan90]

Updated LOTUS_DISABLE_F3 to LOTUS_DISABLE_F3_SUBSYSTEM to provide a clearer description of its function, aligning it with the naming conventions of the other F3-environment variables: ebc04b8

[Kubuxu]

@rjan90 take a look

[Kubuxu]

Looks good to me but I made some changes

[rjan90]

Fixed the failing lint-check in: 8a09991