Type-aware query key parsing using metadata types

Problem

dot query uses generic parseValue() for storage map keys (query.ts:71), but the metadata knows the exact key types. This means users must manually format keys correctly — e.g., wrapping SS58 addresses won't happen automatically like it does for dot tx.

Proposal

Apply the same parseTypedArg() logic that dot tx uses to parse query keys, using the storage item's keyTypeId from metadata.

# Currently fails or requires manual formatting for some key types
dot query System.Account 5GrwvaEF5zXb26Fz9rcQpDWS57CtERHpNehXCPcNoHGKutQY

# With this change: auto-coerces to AccountId32, just like dot tx does

Implementation

• In src/commands/query.ts:71, replace keys.map(parseValue) with metadata-aware parsing
• Use storageItem.keyTypeId to get the expected type from metadata
• Reuse parseTypedArg() from tx.ts (or extract it into a shared utility)

Acceptance Criteria

• dot query System.Account <ss58-address> works with auto-coercion
• Complex key types (tuples, enums) are parsed correctly from CLI args
• Dev account names work as keys where the type is AccountId32

Start in src/commands/query.ts:71 to trace how query keys currently use parseValue, then read parseTypedArg() in tx.ts and the storage metadata path that provides storageItem.keyTypeId. Implement metadata-aware parsing for address, tuple, enum, and dev-account keys, and verify the listed dot query examples work with automatic coercion.