[v10] Development framework

[basfroman]

Summary

This PR introduces a new Development framework for Bittensor SDK.

The framework provides a clean orchestration layer for testing and automating subnet lifecycle operations.
It abstracts low-level Subtensor extrinsics into clear, reproducible steps and now serves as the foundation for all existing E2E tests.

As a result, tests are easier to write, understand, and maintain with clearer structure, better logs, and more consistent behavior during execution.

---

Motivation

Until now, E2E tests relied on direct Subtensor API calls, which led to repeated code, inconsistent patterns, and limited debugging insight.
This framework consolidates those patterns into a single, reusable system built around the TestSubnet class.

TestSubnet standardizes subnet operations such as registration, activation, neuron addition, and hyperparameter updates under one API.
It introduces synchronous and asynchronous execution modes, unified extrinsic responses, and automatic NETUID handling across test runs.

The result is a much more reliable, maintainable, and developer-friendly way to test the Bittensor protocol, both for SDK devs and the broader community.

---

Key Advantages

• Unified, declarative syntax for subnet orchestration.
• Supports both single-step and multi-step execution flows.
• Works in synchronous (execute_steps) and asynchronous (async_execute_steps) modes.
• Automatically injects the correct NETUID for all operations within the same test instance.
• Uses the standardized ExtrinsicResponse type for richer debugging including status, message, fees, receipts, and etc.
• Produces structured, colorized logs that make on-chain activity and errors easy to trace.
• Reduces code duplication and improves readability across all test suites.
• Community-ready: can also be used by subnet operators and researchers to deploy, configure, and test subnet behavior in real or simulated environments.

---

Result

All E2E test suites are now built on this framework.
The codebase is simpler, easier to maintain, and much more transparent during debugging and analysis.

For full technical documentation, see bittensor/extras/dev_framework/README.md.

[thewhaleking]

I really like this, but I think the structure could use some work. Namely having the generated code be gitignored. If you're a user generating methods, you are going to run into merge conflicts when you just want to git pull.