[SDK] Get rid of py-substrate-interface (DO NOT MERGE)

[roman-opentensor]

Context:

The ultimate goal is to focus on async development and no longer depend on the outdated py-substrate-interface library.

At the same time, at least temporarily, we need to maintain backward compatibility with the current implementation of Bittensor SDK. After merging this PR, we will not have to support 2 versions of the code. It will be enough to implement new functions in the asynchronous version and use a wrapper for a sync calls.

Advantages:

• Only asynchronous code needs to be supported
• Easy to understand codebase for community developers
• Possibility of simple deprecation marking for sync method/function calls (without affecting the async ones)
• Support for backward compatibility

AC:

• Implement coroutine executor
• Match list of methods of Subtensor and AsyncSubtensor classes
• Keep backwards compatibility for sync codebase
• Use wrapper calls for Subtensor and sync extrinsics
• Add bittensor.core.chain_data.WeightCommitInfo class for CRv3 data
• Separate the Sabtenso and AsyncSabtensor modules into logical blocks and place the methods in alphabetical order (for the convenience of developers using SDK)
• Implement an async Metagraph with the ability to use it in synchronous code
• Update return object for following methods (make backwards compatible with sync methods):
  • query_constant
  • query_map
  • query_map_subtensor
  • query_module;
  • query_runtime_api
  • query_subtensor
  • state_call
• Add test to compare sync and async Subtensor methods
• Add/Fix/edit/update existed tests:
  • Unit tests
  • Integration tests
  • e2e tests
• Test the functionality on a testnet with a full cycle of operations

Related links:

• Github issue
• Spreadsheet with updated methods and calls

NOTE: This description could be updated

[thewhaleking]

Left one comment that I'm not so sure about. Other than that, LGTM.