[FEATURE REQ] Resolver configured with Synthetic GraphQL is not extracted via Extractor Pipeline

[JamunaraniR]

Release version

ApiOps Tool Kit v4.6.0

Describe the bug

On working with GraphQL Api options, Found that Resolver configured with Synthetic GraphQL is not extracted via Extractor Pipeline. Extractor pipeline extracts apiinformation and specification.graphql only from GraphQL Apis.

Expected behavior

Extractor Pipeline should extract Resolver along with api information and specification.graphql for GraphQL Apis

Actual behavior

Extractor Pipeline does extract Resolver configured with GraphQL Api

Reproduction Steps

1. Add GraphQL Api with schema and Resolver configuration using Synthetic Api Import options.
2. Run the Extractor

[github-actions[bot]]

  Thank you for opening this issue! Please be patient while we will look into it and get back to you as this is an open source project. In the meantime make sure you take a look at the [closed issues](https://github.com/Azure/apiops/issues?q=is%3Aissue+is%3Aclosed) in case your question has already been answered. Don't forget to provide any additional information if needed (e.g. scrubbed logs, detailed feature requests,etc.).
  Whenever it's feasible, please don't hesitate to send a Pull Request (PR) our way. We'd greatly appreciate it, and we'll gladly assess and incorporate your changes.

[JamunaraniR]

Attached Reference screenshot of extractor code output which shows apiinformation.json and specification.graphql but not populating resolver code base