feat(typescript): Add support explicit null values

[amckinney]

Now that the Fern definition supports nullable properties (re: #5601), this upgrades the TypeScript generator to IRv55 to support this feature. For example, consider the following Fern definition:

types:
  User:
    properties:
      name: string
      tags: nullable<list<string>>
      metadata: optional<nullable<Metadata>>

  Metadata:
    properties:
      createdAt: datetime
      updatedAt: datetime
      avatar: nullable<string>
      activated: optional<nullable<boolean>>

The generated TypeScript types look like the following:

export interface User {
    name: string;
    tags: string[] | null;
    metadata?: Metadata | null;
}

export interface Metadata {
    createdAt: Date;
    updatedAt: Date;
    avatar: string | null;
    activated?: boolean | null;
}

Note that this also temporarily disables the dynamic snippet tests so that we can more confidently test the TypeScript SDK generator until example generation is fixed.

[Swimburger]

unrelated, but are we creating a copy of an array here? I think there are simpler ways to do this.

[amckinney]

Yea it looks like it - I have a feeling this is because we always map over the array values and (optionally) perform a string mapper function (e.g. item.toString()), so it's simpler to always use the .map expression.

We can take a closer look here though.

[github-actions]

🌿 Preview your docs: https://fern-preview-8c818a62-ea74-442b-9653-10f92a200675.docs.buildwithfern.com/learn