Upgrade Polkadot SDK to stable2503-6

[l0r1s]

Description

This PR is part of #1594 includes all necessary changes to upgrade to polkadot-stable2503-6.

Changes:

• Frontier dependencies: Updated rev to opentensor/frontier@c591df98

• sc-consensus-grandpa patch: Updated rev to opentensor/grandpa@67ff75e9

• BLS patch: Added a patch for paritytech/bls@004e1aee (commit for no_std support), backported on top of the currently locked 1.3.0 version due to timelock requirements.

  Note: This will likely need to be updated in the future as it involves a rework of the consuming code. See [opentensor/bls@a8598e5](https://github.com/opentensor/bls/commit/a8598e5ef7847c2f6bf7240593ddb07fef0c8cd2)

• Substrate-fixed repo: Switched from opentensor/substrate-fixed to the upstream encointer/substrate-fixed to incorporate the latest changes (e.g. DecodeWithMemTracking derives).

• Dependency and edition management: Centralized all dependency and edition declarations at the workspace root to simplify maintenance.

• Feature flags: Disabled default-features at the workspace root and enabled necessary features on a per-crate basis.

• Node updates (following psdk upgrade):

  • Removed network_starter (no longer needed).
  • Removed the option to select the P2P networking library.

• WASM compilation fix: Resolved runtime compilation issues with wasm32v1-none.

• Rust upgrade: Bumped Rust to the latest 1.88.0 and switched the target from wasm32-unknown-unknown to wasm32v1-none.

• Type derives: Added DecodeWithMemTracking derives for all necessary types.

• Runtime binary cleanup: Removed the spec_version binary from the runtime to avoid compilation errors.

Related Issue(s)

• 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]

amazing!