Create `byName` index on `subgraph_domains` table

[tk-o]

We attempted adding the index once:

• add missing index on domain name column #1747
  but the udpate has introduced a bug where Ponder would fail to create indexed in ENSDb with the following message:

06:06:57.641 WARN  Failed database query query=create_indexes query_id=71db0ec7 (13ms)
error: index row requires 23456 bytes, maximum size is 8191

The root cause analysis was documented in this Slack thread and the possible fix was added in this PR:

• WIP Set max character count for byName index in subgraph_domains table #1815

However, due to feedback raised by AI agents reviewing the PR, the team decided to revert changes from PR #1747 and design another solution to enable byName index on subgraph_domains table.

[coderabbitai]

🔗 Related PRs

#1655 - Registration/Renewal Superceding Refactor [merged]
#1711 - Fix writes through ENSDb Client [merged]
#1746 - add missing subgraph schema indexes [merged]
#1747 - add missing index on domain name column [merged]
#1778 - ENSDb SDK: group database schema objects [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[lightwalker-eth]

Additional ideas for resolving this shared by @shrugs in Slack here: https://namehash.slack.com/archives/C086Z6FNBHN/p1774377708838169?thread_ts=1774332923.237389&cid=C086Z6FNBHN

[shrugs]

a hash(name) index would support the exact name lookups without the size limit, then to handle the partial searches gin (name gin_trgm_ops) should work, and neither would require updates to the generated sql