feat(paych): add EnablePaymentChannelManager config option

[sumitvekariya]

add EnablePaymentChannelManager config option to disable payment channel manager by default

This change introduces a new configuration option EnablePaymentChannelManager to control whether the payment channel manager is started on node startup.

• Added EnablePaymentChannelManager boolean field to FullNode config struct
• Set default value to false (disabled by default) since payment channels get minimal use on mainnet
• Added conditional wiring in node/builder_chain.go to only start payment channel manager when config option is enabled
• Updated config documentation with clear description of the option

This saves resources for light nodes and most full nodes that don't use payment channel functionality, while still allowing users to enable it when needed by setting EnablePaymentChannelManager: true in their config.

Related Issues

#12718

Proposed Changes

• Config Addition: New EnablePaymentChannelManager boolean field in FullNode config struct
• Default Behavior: Payment channel manager disabled by default (false)
• Conditional Service Wiring: Modified dependency injection in node/builder_chain.go to only wire payment channel services when enabled
• Documentation: Updated config auto-generated documentation
• Changelog: Added entry to UNRELEASED section following contribution conventions

Additional Info

• Backward Compatibility: Full backward compatibility maintained - users can enable payment channels by setting EnablePaymentChannelManager: true
• Resource Savings: Eliminates unnecessary resource usage for nodes that don't use payment channels
• Testing: All existing payment channel tests pass, config tests updated with new default

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

[Copilot]

Pull Request Overview

This PR adds a new configuration option to control the initialization of the payment channel manager. It introduces the boolean field EnablePaymentChannelManager, sets its default value to false, and conditionally wires the payment channel components in the node builder based on this flag.

• Added the EnablePaymentChannelManager field to the FullNode config struct.
• Updated the default configuration, documentation, and dependency injection in the node builder.
• Removed the unconditional wiring of payment channel services and replaced it with conditional wiring.

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File	Description
node/config/types.go	Added configuration field and documentation comments.
node/config/doc_gen.go	Updated auto-generated documentation to include the new option.
node/config/def.go	Set default value for the new EnablePaymentChannelManager field.
node/builder_chain.go	Replaced unconditional wiring of payment channel components with conditional wiring based on the configuration flag.

[rvagg]

too many edits in this file, please back out the 3 edits below line 11

[sumitvekariya]

agreed, removed all the 3 changes below line 11

[rvagg]

I think this is fine. Need some removals in CHANGELOG.md, make gen is needed to get CI to run and I'd like to do some tests with this locally.

For the record, the thing that bothers me about the payment channel manager is that it actively listens to head changes and looks for messages that match its schema of things to act on. Mostly this is a very minor activity, hardly measurable. But it does become measurable when you're running in lite mode, pointing to a remote, where head change listening requires API calls. I ran into this problem when doing gateway rate limiting because the gateway is effectively a lite client. So I expect that test will fail here and need to be adjusted.

It's not a huge concern, this is just a minor cleanup and we're not removing payment channel functionality or touching anything on chain. We're just preventing a node participating in payment channels while this option is turned off but it can easily be turned on again if ever required.

[rvagg]

Odd DI errors assembling lotus:

        	            	    missing type:
        	            	    	- *paychmgr.Manager (did you mean to Provide it?)

In theory, paychmgr.Manager shouldn't be needed with that chunk of code moved into a conditional in builder_chain.go, only this: Override(new(*paychmgr.Manager), modules.NewManager) and this: Override(HandlePaymentChannelManagerKey, modules.HandlePaychManager) should be caring about it as far as I can tell. So there must be some downstream dependency that depends on it indirectly. I'm just not seeing it. This will need some investigation and experimentation. @sumitvekariya you're welcome to tinker further with this to try and get to the bottom of it. The uber/fx framework (for DI / Direct Injection) we use in builder_chain.go is basically defining how to make the components and then it's up to the DI framework then uses that knowledge to piece together what it needs for a final Lotus instance. The error is suggesting that something still needs a *paychmgr.Manager but we've branched out the part where we tell it how to make one. So we need to figure out who needs it still.