backport: bitcoin/bitcoin#24304: [kernel 0/n] Introduce bitcoin-chainstate

[knst]

Issue being fixed or feature implemented

This PR sum up all changes that are required to backport bitcoin#24304 and proof-of-concept that it is possible after just couple extra tiny steps.

The first blocker is already have PR: #7178

What was done?

Beside changes that already has been merged or having PRs such as #7178 [in review], #7070, #7008, #6992, #6959, #7106 (by Udjin), #7065 (by kwvg) and many other PRs:

• drop dependency of InstantSend on CActiveMasternodeSync
• drop dependency of InstantSend on CChainState
• new stub implementation NullNodeSyncNotifier of CActiveMaternodeSync for governance
• further refactorings of CGovernanceManager to reduce dependencies on other components
• add guards for CTxMempool is nullptr [which could be for chainstate case]
• removed multiple includes of msg_result.h over codebase
• moved multiple functions between modules to reduce extra dependencies
• done the backport kernel zero [kernel 0/n] Introduce bitcoin-chainstate bitcoin/bitcoin#24304 which unblocks the whole multiple series of all kernel backports

There are several dirty hacks that meant to be fixed and they will be done by extra PRs; local branches for these fixes are semi-ready:

• CDKGSessionManager should be split to network & non-network pieces. For right now a workaround for linkage is used by moving some code to net_processing.cpp
• CSporkManager - the same workaround as CDKGSessionManager
• llmq::utils::EnsureQuorumConnections and llmq::utils::AddQuorumProbeConnections - the same workaround
• CQuorumManager::RequestQuorumData should be moved away to avoid network dependencies

There are several dependencies of dash-chainstate that looks excessive, but they are not a blocker and may be removed in any time in the future:
- base58.cpp
- core_write.cpp
- evo/core_write.cpp
- key_io.cpp
- node/interface_ui.cpp
- protocol.cpp
- scheduler.cpp
- node/bloom.cpp
- index/txindex.cpp
- batchedlogger.cpp
- Reduce governance significantly so far as there's no actual governance enabled in chainstate mode (governance is out of blockchain anyway)
- Reduce llmq dependencies, probably to drop: dkgsession, dkgsessionmgr, dkgsessionohandler, debug
- Remove CSigningManager from LLMQContext. LLMQContext should be quorum-only-context; CSigningManager should be inside active/

How Has This Been Tested?

Build succeed with bitcoin#24304, functional & unit tests runs

Run dash-chainstate:

$ src/dash-chainstate /home/knst/.dashcore/
Hello! I'm going to print out some information about your datadir.
        Path: "/home/knst/.dashcore"
        Reindexing: false
        Snapshot Active: false
        Active Height: 2294070
        Active IBD: true
        CBlockIndex(pprev=0x5654a3bdb218, nHeight=2294070, merkle=5c87e557b9e697e9308a4a6bd684e362910fe418ca60e59ae1376e91c487df77, hashBlock=0000000000000010938b2d1c2f1ff08163dae17f4196a41d73b9e6e3c4114cc2)

Breaking Changes

N/A

Checklist:

Go over all the following points, and put an x in all the boxes that apply.

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated relevant unit/integration/functional/e2e tests
• I have made corresponding changes to the documentation
• I have assigned this pull request to a milestone (for repository code-owners and collaborators only)

[github-actions]

This pull request has conflicts, please rebase.

[github-actions]

⚠️ Potential Merge Conflicts Detected

This PR has potential conflicts with the following open PRs:

• fix: collect sigshares synchronously in dispatcher for parallel verification #7225 - fix: collect sigshares synchronously in dispatcher for parallel verification

Please coordinate with the authors of these PRs to avoid merge conflicts.