Extract NiPoPow

[ccellado]

See #1965

Classes moved from src -> ergo-core/src

Some refactoring decoupling has to be made:

Extraction:
    - From mining/CandidateGenerator
      - deriveUnprovenHeader into mining/CandidateUtils
    - From reemission/ReimissionRules
      - Extract object into ReemissionRulesUtils
    - From ErgoSettings
      - Extract object into ErgoSettingsReader (stay in ergo-node)
    - From ErgoMempool
      - Extract object types into ErgoMempoolTypes
    - From nodeView/history/extra/ExtraIndexer
      - Extract trait ExtraIndex
    - From ErgoNodeViewSynchronizer
      - Extract ReseiveableMessages into ErgoNodeViewSynchronizerMessages
    - From BlockchainApiRoute
      - Extract SortDirection
    - From ErgoApp
      - Extract CriticalSystemException
    - From ErgoNodeViewHolder
      - Extract LocallyGeneratedModifier

[kushti]

@ccellado so if the main motivation for the core module I guess is to extract to there functionality needed for building alternative clients just. Then I guess node-specific parts should not be there, only consensus-related and p2p-related objects and functions ,so following parts should be moved away from it:

• /history/extra , /history/storage and all the classes in /history but ErgoSyncInfo (which is used in p2p)
• nodeview/mempool (aside of TransactionMembershipProof)
• /http/api/requests, /scorex/api/http/ApiError
• /scorex/core/network/peer, ConnectedPeer, ConnectionDirection

From org.ergoplatform.settings, makes sense to have ChainSettings, ValidationRules, Parameters, PeerFeatureDescriptors, removing NodeSettings etc

[ccellado]

- Extraction additional
  - From settings/Constants
    - mode modifierSerializers to ErgoNodeViewSynchronizer
  - From nodeView/history/ErgoHistory
    - types and constants to ErgoHistoryConstants
  - From http/api/ApiCodecs
    - Requests codecs into ApiRequestsCodecs
    - Extra codecs into ApiExtraCodecs

But there is a problem with ErgoState. Looks like it should not be in core

[ccellado]

Moved ErgoTransaction (which depends on ErgoStateContext which depends on ErgoSettings) and subsequent thing out of core, but ValidationRules depend on it

[ccellado]

Do we need ValidationRules in core? Maybe not all of them

[ccellado]

  - From ApiCodecs
    - Move NodeView codecs
  - From scorex.core.network.message.Message
    - Move constants into MessageConstants
  - From scorex.core.network.message.BasicMessageRepo
    - SyncInfoMessageSpec

1. PeerFeatureDescriptors depends on ModeFeatureSerializer which requires NodeConfigurationSettings
2. PeerSpec (required by Handshake) depends on LocalAddressPeerFeature, RestApiUrlPeerFeature from scorex.core.network.peer

[ccellado]

Rebased onto 5016-refactor

  - From ErgoHistory
    - heightOf into ErgoHistoryUtils
  - From NodeConfigurationSettings
    - ClientCapabilities
    - UtxoSettings
    - NipopowSettings
  - From nodeView/state/StateType
    - to ergo-node Evidence into StateTypeErgo