CLI Typegen expand references

Start by locating the CLI typegen implementation and its typegen configuration handling. Review how schema references and GROQ query types currently produce internalGroqTypeReferenceTo, then determine how configuration or schema flags should control expansion and how multi-level references should be represented. Done means generated TypeScript types expose the referenced schema properties without requiring a dummy query.

Is your feature request related to a problem? Please describe.
When generating types you only get an "internalGroqTypeReferenceTo" a related schema.

export type ProgressBar = {
  _id: string;
  _type: "progressBar";
  _createdAt: string;
  _updatedAt: string;
  _rev: string;
  name: string;
  steps: Array<{
    _ref: string;
    _type: "reference";
    _weak?: boolean;
    _key: string;
    [internalGroqTypeReferenceTo]?: "progressBarStep";
  }>;
  locale?: string;
};

This means that you can't access the actual properties on an indiviual "step", which becomes troublesome when you have several references to other schemas or some kind of multi-level-reference structure (e.g. I have a Page with a Progress bar that has Progress bar steps).

Describe the solution you'd like
It would be great if we during the type generation could define if we wanted all/some "internalGroqTypeReferences" expanded. Perhaps either via the typegen config or some kind of flag on the schema itself.

The result after such an expansion could be something like:

export type ProgressBar = {
  _id: string;
  _type: "progressBar";
  _createdAt: string;
  _updatedAt: string;
  _rev: string;
  name: string;
  steps: Array<{
    _ref: string;
    _type: "reference";
    _weak?: boolean;
    _key: string;
    [internalGroqTypeReferenceTo]?: "progressBarStep";
    // Progress bar step properties
    _id: string;
    _type: "progressBarStep";
    _createdAt: string;
    _updatedAt: string;
    _rev: string;
    text: string;
    percentage: number
    locale?: string;
  }>;
  locale?: string;
};

Describe alternatives you've considered
I've considered creating a "dummy query" that explicitly expands the type but isn't used anywhere, however I don't think that's a very clean solution. I've also tried to alter the main query that contains multi-level-references to try and get the query-typegen to expand the "deeper levels of nesting" but with no success.

Additional context
Typegen is a super helpful feature, and the current state is a very promising! I do however think that there is room for some improvement, an this would bring it a big step forward!