Database, CP Node, Version Checks

[reinamora137]

This may lead to further discussion around version pinning on the requirements.txt modules, but the most important is finalizinng/verifying the index on each CP version.

Some db version checks for reference are here: https://github.com/stampchain-io/btc_stamps/pull/75/files#diff-f616c782943a0e1948d5c234c45d041ce3478102ccd58bb37ab359975fd7397cL142-L187

Also see def get_cp_version(): in xcprequest.py. We just need to add the versions we have validated in check.py so the indexer stops if the user is hitting a version we have not validated.

[reinamora137]

CP has been staying in consensus with all the current upgrades. Testing across multiple 10.x and 9.x nodes continues without interruption in stamp numbering.

[reinamora137]

consensus changes coming in CP version 10.3 which we will want to check to validate that version is in use