Align Crust registry address overrides with MultiAddress compatibility

[Copilot]

Checklist

• Use the owner account that submitted registrar_reserve to sign the project information, and fill in the signature.

• After each update of the project information, please sign the latest data and submit the signature.

• Add a description for your pr, the description includes the original data.

• Fill up the signature of the original data, signature account to Signature Auto check.

• Compatibility update summary

  • Crust’s registry still mapped address types to AccountId, which can break consumers expecting modern Substrate MultiAddress semantics. This change aligns Crust’s override with current address compatibility expectations.

• Changes

  • Type override alignment
    • In assets/registry/crust-parachain.js, updated:
      • Address: 'AccountId' → Address: 'MultiAddress'
      • LookupSource: 'AccountId' → LookupSource: 'MultiAddress'

• Example

  types: {
    Address: 'MultiAddress',
    LookupSource: 'MultiAddress'
  }

Signature Auto check

Para ID Owner & Signature Account:
<REPLACE THE OWNER>

Data that needs to be signed:
assets/registry/crust-parachain.js

Signature Hash: <REPLACE THE SIGNATURE>