Sponsor chain name creation

[CedrikNikita]

Note

High Risk
Introduces new on-chain transaction flow that spends from a configured private key and adds new persistent tables + background cron retries, so misconfiguration or logic bugs could cause failed claims or unintended spend.

Overview
Adds a new sponsored AENS chain-name claiming feature under /profile/chain-name, including endpoints to create a wallet-signing challenge, submit a claim request, and query claim status.

Implements persistent claim/challenge storage (new TypeORM entities + SQL migration), a background cron-driven state machine to preclaim/claim/update/transfer names with retries/backoff, and introduces shared signature verification via a new verifyAeAddressSignature utility (used by both chain-name claiming and the existing X-invite challenge flow).

Extends configuration/deploy pipelines to provide PROFILE_CHAIN_NAME_PRIVATE_KEY and related retry/TTL settings so deployments can sponsor on-chain transactions.

^{Written by Cursor Bugbot for commit efaf6f9. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}