Update `lib/query/query-keys.ts` to use codegen-generated keys

[0xdevcollins]

Depends on: #100

The codegen with exposeQueryKeys: true generates query key constants for each operation. We should use these instead of the hand-written bountyKeys factory.

Tasks

• Review generated key exports from generated.ts
• Replace bountyKeys in lib/query/query-keys.ts with re-exports from generated.ts
• Update all hook files and prefetch.ts to use the generated keys
• Remove redundant hand-written key factories

Acceptance Criteria

• Single source of truth for query keys (codegen)
• All cache invalidation uses generated keys

[linear]

BOU-100

[coderabbitai]

🔗 Related PRs

#30 - feat: Implement React Query hooks for managing bounties [merged]
#32 - feat: introduce TanStack Query integration for bounties, including query options, keys, and prefetching utilities. [merged]
#45 - Ekene001/bou 59 setup graphql client code generation [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!

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 100 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[SamixYasuke]

@SamixYasuke has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hello, I'd like to handle this issue, thanks.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @SamixYasuke to this issue.

[Chucks1093]

@Chucks1093 has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

I am a highly skilled frontend developer and will make sure I submit a pr that matches the intended result in this issue.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Chucks1093 to this issue.

[SudiptaPaul-31]

@SudiptaPaul-31 has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

May I be assigned to this issue I have worked on several open-source projects and also an active open-source contributor and would love to contribute to this issue. I have worked with more than 30+ open-source projects and delivered quality pr's for them which led to faster project delivery

ℹ️ Repo Maintainers: To accept this application, review their application or assign @SudiptaPaul-31 to this issue.

[Favour4712]

@Favour4712 has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

I am a fullstack blockchain developer, assign this to me and I will deliver in few hours

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Favour4712 to this issue.