Narrative Overhaul: enssdk integration tests with example-queries.ts

[shrugs]

Broken out from #1793.

enssdk's integration test (packages/enssdk/src/omnigraph/module.integration.test.ts) only exercises a HelloWorld query. Wire up the shared example-queries.ts (currently at packages/ensnode-sdk/src/omnigraph-api/example-queries.ts) so the thin client is exercised end-to-end against the devnet via integration-test-env.

From #1793:

We should integrate the client libs into the integration test environment and confirm that those pathways operate against the devnet as expected. This sort of integration test over the (thin) clients would be much more valuable than mocking the api responses, since there's very little actual control flow in most of the client methods to test.

[coderabbitai]

🔗 Related PRs

#1660 - ENSDb data model [merged]
#1711 - Fix writes through ENSDb Client [merged]
#1729 - ENSApi Integration Tests in CI [merged]
#1855 - feat(ensapi): add tracing support with Pothos plugins and enhance GraphQL execution tracing [merged]
#1867 - enskit omnigraph: react bindings, id refactoring, schema improvements [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!