Document CRN-specific scoring rules

[aliel]

Adds an Additional rules for Compute Resource Nodes section to the scoring page (docs/nodes/resources/scoring/index.md), documenting the CRN-only checks that were missing:

• Stable IP addresses — static IPv4/IPv6 required; 2 or more IPv4 or IPv6-range changes over a rolling 30-day window are flagged. IPv6 is keyed to the node's VM address pool (IPV6_ADDRESS_POOL), not the access address. The window is rolling, so the score recovers as changes age out.
• One scored node per machine — when several CRNs share an IPv4 or IPv6 pool, only the verified-or-earliest node keeps its score; the rest are set to 0. NAT/reverse-proxy caveat included.
• Liveness (active / inactive / dead) — 24h proof-of-CRN; a dead node's score is set to 0.
• Diagnostic codes table (1001–1007).

An info note states the rules are rolled out progressively, with warning codes published before a rule affects the score.

Notes for reviewers:

• The 30-day IP-stability window matches the intended deployment setting (the scoring default is currently 365 days; deployment sets IP_STABILITY_WINDOW).
• These rules ship on the updated scoring service; timing the publish with that rollout is recommended.

[github-actions]

Deployed on:

• https://bafybeigitahd6bug6zbt3z3u4y6fwqgcybezir3ns627kmiwygpx34qeym.ipfs.aleph.sh

Preview for this pull request, updated on every commit and removed once the PR is closed.

[foxpatch-aleph]

This PR adds a well-structured, clearly written section documenting CRN-specific scoring rules. The diagnostic code table is complete and maps correctly to the rules described in the text. Internal links and anchors are valid, terminology (IPV6_ADDRESS_POOL, /status/config) is consistent with the installation guides, and the VitePress container syntax matches the rest of the docs. The content accurately distinguishes the 30-day rolling IP-stability window from the 2-year performance window, explains the liveness thresholds, and includes appropriate operator-facing warnings about NAT/shared-IP scenarios. No correctness, security, or quality issues found.

docs/nodes/resources/scoring/index.md (line 146): Minor: diagnostic code 1007 ("Not currently proving it is a CRN") corresponds to the "inactive" status, but the Liveness section only states that "dead" nodes get a score of 0. It might help to clarify whether 1007 is purely informational or if it can affect the score during the progressive rollout — an operator seeing this code may wonder if their score is impacted. The top-level info note about warnings covers this implicitly, but an explicit note would reduce support questions.