Add getNetworkRegistrationBlock view to SubnetPrecompile

[fine135]

Description

Adds getNetworkRegistrationBlock(uint16) as a view function to SubnetPrecompile, allowing smart contracts to query the block number at which a given subnet was registered. The function reads directly from NetworkRegisteredAt storage and explicitly records db_read_gas_cost so callers are correctly charged when invoked from within a contract.

Also adds the corresponding ABI entry to contract-tests/src/contracts/subnet.ts and an e2e test in contract-tests/test/precompileWrapper.direct-call.test.ts.

Related Issue(s)

• Relates 2455

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

N/A

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 ./scripts/fix_rust.sh 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)

N/A

Additional Notes

The function follows the same pattern as other view functions in SubnetPrecompile (e.g. getServingRateLimit), with the addition of explicit gas metering via handle.record_cost(RuntimeHelper::<R>::db_read_gas_cost()) - unlike the existing view functions which omit this.

[open-junius]

Thanks for the contribution. I will scan all view functions defined in precompiles, record the cost of reading data from storage.

[l0r1s]

Looks good, @fine135 you need to merge devnet-ready and then bump spec version and we should be good to merge

[fine135]

Done! @l0r1s @open-junius I've merged devnet-ready and bumped the spec version to 414.

[fine135]

Hi @l0r1s and @JohnReedV, it looks like there are merge conflicts in lib.rs again. Should I merge the devnet-ready branch and bump the version one more time?
Also, to avoid these recurring conflicts while the PR is waiting, is there a better workflow I should follow? For example, should I ping you on Discord once it's green? I'd love to get this merged smoothly. Thank you!

[fine135]

Hi @l0r1s @JohnReedV @sam0x17, just a quick update: I've merged devnet-ready and bumped the version in lib.rs, so the conflicts are resolved. Could you please give it a quick review and merge it when you have a moment? I'm hoping to get it in before any new conflicts pop up. Thanks!