localnet improvement

[open-junius]

Description

The feature will improve the localnet configuration for testing.

tasks

• REQ-LOCNET-001: Configure "pow-faucet" feature for registrations

• Enable the "pow-faucet" feature for the Localnet configuration.

• This feature should be used to manage registrations in the Localnet environment.

• REQ-LOCNET-002: Set initial max registrations per block to 1000

• Update the SubtensorInitialMaxRegistrationsPerBlock constant to 1000.

• This should only apply when the "pow-faucet" feature is enabled.

• REQ-LOCNET-003: Set initial target registrations per interval to 1000

• Update the SubtensorInitialTargetRegistrationsPerInterval constant to 1000.

• This should only apply when the "pow-faucet" feature is enabled.

• REQ-LOCNET-004: Create subnet 1
  Not in subtensor side, we will use btcli to create.

• REQ-LOCNET-005: Remove subnet 3

• Subnet 3 should not be present in the Localnet configuration.

• Any references or dependencies on subnet 3 should be removed from the Localnet codebase.

• REQ-LOCNET-006: Create predefined accounts with specific roles
  Not in subtensor side, we will use btcli to create. And pre-defined accounts are the same as balances.

• REQ-LOCNET-007: Set specific TAO balances for predefined accounts
  pre-defined accounts are the same as balances in local chain setting.

• REQ-LOCNET-008: Implement account creation and balance setting on Localnet initialization

Related Issue(s)

• Closes #[issue number]

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Other (please describe):

Breaking Change

If this PR introduces a breaking change, please provide a detailed description of the impact and the migration path for existing applications.

Checklist

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have run cargo fmt and cargo clippy to ensure my code is formatted and linted correctly
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

Screenshots (if applicable)

Please include any relevant screenshots or GIFs that demonstrate the changes made.

Additional Notes

Please provide any additional information or context that may be helpful for reviewers.

[sam0x17]

LGTM! ran locally and was easy to configure