feat: Add useOperationIdAsQueryKey option for query key generation

[mortik]

Summary

Fix #2096

This PR adds a new configuration option useOperationIdAsQueryKey that allows users to generate query keys using the OpenAPI operation ID instead of the route string for TanStack Query implementations.

Changes

• Added useOperationIdAsQueryKey?: boolean to QueryOptions and NormalizedQueryOptions types
• Modified query key generation logic in packages/query/src/index.ts to use operation ID when enabled
• Updated normalizeQueryOptions function to handle the new option
• Added comprehensive tests in packages/query/src/utils.test.ts
• Added documentation in /docs/src/pages/reference/configuration/output.md

Configuration Example

module.exports = {
  petstore: {
    output: {
      client: 'react-query',
      override: {
        query: {
          useOperationIdAsQueryKey: true,
        },
      },
    },
    input: './petstore.yaml',
  },
};

[mortik]

This should resolve #2096

[AllieJonsson]

LGTM!

[mortik]

I realized that this approach still needs an update to include the path params like id etc. i will update the pr to include that in the querykey function

[soartec-lab]

Please give me a little time to salvage past discussions about cases where you might want to use arbitrary strings for query keys. And once a policy has been decided, it will need to be documented in the documentation to avoid any confusion.