fix: accept both lowercase and checksum starknet address as valid

[wa0x6e]

This PR loosen the starknet address validator, to accept both checksum (current) and lowercase (new) addresses as valid. It stil require that addresses are fully padded.,

This will align with the evmAddress validation, which is currently accepting both lowercase and checksum.

Without this patch, the validator will reject all checksum starknet address. In the ui side, we don't check for case when sending starknet address (like adding member in the space settings), so valid data on the UI will be rejected by sequencer.

[Copilot]

Pull Request Overview

Loosens the Starknet address validator to accept both lowercase and checksum addresses by comparing values in lowercase, aligning it with the existing evmAddress behavior.

• Replaces strict equality check with a lowercase comparison in the Starknet address format validator.
• Ensures both checksum and lowercase Starknet addresses pass validation.

Comments suppressed due to low confidence (2)

src/utils.ts:135

• No unit tests were updated to cover the new acceptance of both lowercase and checksum Starknet addresses. Consider adding tests for both formats to ensure the validator behaves as expected.

return (

src/utils.ts:136

• [nitpick] Consider updating documentation or inline comments to clarify that the starknetAddress format now accepts both lowercase and checksum addresses.

validateAndParseAddress(value).toLowerCase() === value.toLowerCase()

[bonustrack]

Is there a way to double vote if we support both casing? I believe in the hub db we have only checksummed address, not lowercased ones

[wa0x6e]

Is there a way to double vote if we support both casing? I believe in the hub db we have only checksummed address, not lowercased ones

We already support both casing for evm address

On the backend side, we have another compare after lowercasing everything

[bonustrack]

utACK