interfaceName on array fields is somehow misleading.

[tobiastom]

A long time ago #2709 introduced the interfaceName property on array and other combined files. While this is excellent, I can currently let Payload generate a specific Typescript type to represent one of the items.

Given the example from the pull request, modified to the array case, this is the current behavior:

{
  type: 'array',
  name: 'meta',
  interfaceName: 'SharedMeta',
  fields: [
    {
      name: 'title',
      type: 'text',
    },
    {
      name: 'description',
      type: 'text',
    },
  ],
},

payload will generate something like this:

export type SharedMeta = 
  | {
  title?: string;
  description?: string;
  }[]
  | null;

export interface Collection1 {
  meta?: SharedMeta;
}

Unfortunately with this, I cannot use the type of one of the items in other parts of the code. I also tried to use Array<SharedMeta> and SharedMeta[], but special characters are just filtered out. Would it make sense to change the behaviors for array types to use the interfaceName as an inner type, or allow the usage of some kind of array notation in it?

Right now I'm defining my own type like this:

export type SharedMetaItem = NonNullable< SharedMeta >[number];

but this feels kind of wrong. Any ideas?