fix: support prefix matching in v2 display field validation

[lcastillo-ledger]

Summary

• Fix false positive errors/warnings in v2 display field validation when descriptors use array root paths
• Use data_path_starts_with prefix matching instead of strict set equality when comparing format paths against ABI paths

Context

The v2 display field linter validates that format paths correspond to actual ABI paths and vice versa. It was using strict set difference, which fails when a descriptor defines a display field for an array root (e.g. entries.[]) while the ABI expands into individual leaf paths (e.g. entries.[].alias, entries.[].address).

This caused:

• Spurious "Invalid display field" errors for format paths like entries.[] that don't exist as exact ABI paths but are valid prefixes
• Spurious "Missing display field" warnings for ABI leaf paths like entries.[].alias that are already covered by a parent format path

With prefix matching:

• A format path is valid if it matches an ABI path exactly or is a prefix of one
• An ABI path is considered covered if a format path matches it exactly or is a prefix of it

Test plan

• Lint a descriptor with array root display fields (e.g. Safe AddAddressBookEntry with entries.[].alias) → no false positive errors
• Lint a descriptor with exact leaf paths → behavior unchanged
• Lint a descriptor with a truly invalid path → still reports error correctly

Made with Cursor