Is your feature request related to a problem? Please describe.

I'm always frustrated when:

• we have a config that is true for all networks yet it has to be configured explicitly
• we have a lot of top level configs without logical grouping

Describe the solution you'd like

1. Create an fschain.disable_autodeploy with an inverse meaning, we use autodeploy by default, but don't if disable_autodeploy is true. This config shouldn't be used normally, only in case of emergency/node failing to work with autodeploy for whatever reason (although practically it's super-stable now).
2. Make fschain_autodeploy default to true, but support it for one more release (simplifying transition).
3. In subsequent release drop fschain_autodeploy completely.

Describe alternatives you've considered

Keeping things as is is not very convenient.

Additional context

#2423.