[REPLAY-2] Orchestration Service supports option to prefer configured integrity hashes

[ericpassmore]

By default, expected integrity hashes are overwritten. Provide --use-configured-hash option when starting orchestration service. When enabled

• If the configuration has an expected integrity hash this will be used to validate replay
• The replay script will understand this option, and skip the steps of posting back start block integrity hash
• The replay script will instead directly load the snapshot and sync until end block
• If the configuration does not have a value for expected integrity hash the normal process will continues as before
• The replay script will loading snapshot, terminate nodeos, and starting read only nodes, and posting back start block integrity hash
• Following that the nodes will continue to sync to end block, and continue normal operations

Another option to --protect-configured-hash is similar. It will make sure the expected hash with a value can not be overwritten with None. It will allow new hashes values to be set over the old value.