workerd: `IncomingRequestCfProperties` is missing geo data

Hello,

This issue pertains to @cloudflare/worker-types. I would open a pull request as I have the issue resolved in my local package, but I’m not sure how the type generation works in this repo.

The issue is that IncomingRequestCfProperties is not including the IncomingRequestCfPropertiesGeographicInformation.

IncomingRequestCfProperties are currently generated as:

declare type IncomingRequestCfProperties<HostMetadata = unknown> =
  IncomingRequestCfPropertiesBase &
    IncomingRequestCfPropertiesBotManagementEnterprise &
    IncomingRequestCfPropertiesCloudflareForSaaSEnterprise<HostMetadata> &
    IncomingRequestCfPropertiesGeographicInformation &
    IncomingRequestCfPropertiesCloudflareAccessOrApiShield;

Which is fine, but the IncomingRequestCfPropertiesGeographicInformation is omitted from the export as it is a union type and not an interface.

Currently the following is generated for IncomingRequestCfPropertiesGeographicInformation:

/**
 * Geographic data about the request's origin.
 */
declare type IncomingRequestCfPropertiesGeographicInformation =
  | {}
  | {
      /** The country code `"T1"` is used for requests originating on TOR  */
      country: "T1";
    }
  | {
      /**
       * The [ISO 3166-1 Alpha 2](https://www.iso.org/iso-3166-country-codes.html) country code the request originated from.
       *
       * If your worker is [configured to accept TOR connections](https://support.cloudflare.com/hc/en-us/articles/203306930-Understanding-Cloudflare-Tor-support-and-Onion-Routing), this may also be `"T1"`, indicating a request that originated over TOR.
       *
       * If Cloudflare is unable to determine where the request originated this property is omitted.
       *
       * @example "GB"
       */
      country: Iso3166Alpha2Code;
      /**
       * If present, this property indicates that the request originated in the EU
       *
       * @example "1"
       */
      isEUCountry?: "1";
      /**
       * A two-letter code indicating the continent the request originated from.
       *
       * @example "AN"
       */
      continent: ContinentCode;
      /**
       * The city the request originated from
       *
       * @example "Austin"
       */
      city?: string;
      /**
       * Postal code of the incoming request
       *
       * @example "78701"
       */
      postalCode?: string;
      /**
       * Latitude of the incoming request
       *
       * @example "30.27130"
       */
      latitude?: string;
      /**
       * Longitude of the incoming request
       *
       * @example "-97.74260"
       */
      longitude?: string;
      /**
       * Timezone of the incoming request
       *
       * @example "America/Chicago"
       */
      timezone?: string;
      /**
       * If known, the ISO 3166-2 name for the first level region associated with
       * the IP address of the incoming request
       *
       * @example "Texas"
       */
      region?: string;
      /**
       * If known, the ISO 3166-2 code for the first-level region associated with
       * the IP address of the incoming request
       *
       * @example "TX"
       */
      regionCode?: string;
      /**
       * Metro code (DMA) of the incoming request
       *
       * @example "635"
       */
      metroCode?: string;
    };

This should be converted to an interface so the intersection IncomingRequestCfProperties type is valid. It should be changed to something like:

/**
 * Geographic data about the request's origin.
 */
declare interface IncomingRequestCfPropertiesGeographicInformation {
  /**
   * The [ISO 3166-1 Alpha 2](https://www.iso.org/iso-3166-country-codes.html) country code the request originated from.
   *
   * If your worker is [configured to accept TOR connections](https://support.cloudflare.com/hc/en-us/articles/203306930-Understanding-Cloudflare-Tor-support-and-Onion-Routing), this may also be `"T1"`, indicating a request that originated over TOR.
   *
   * If Cloudflare is unable to determine where the request originated this property is omitted.
   *
   * @example "GB"
   */
  country?: Iso3166Alpha2Code | 'T1';
  /**
   * If present, this property indicates that the request originated in the EU
   *
   * @example "1"
   */
  isEUCountry?: "1";
  /**
   * A two-letter code indicating the continent the request originated from.
   *
   * @example "AN"
   */
  continent?: ContinentCode;
  /**
   * The city the request originated from
   *
   * @example "Austin"
   */
  city?: string;
  /**
   * Postal code of the incoming request
   *
   * @example "78701"
   */
  postalCode?: string;
  /**
   * Latitude of the incoming request
   *
   * @example "30.27130"
   */
  latitude?: string;
  /**
   * Longitude of the incoming request
   *
   * @example "-97.74260"
   */
  longitude?: string;
  /**
   * Timezone of the incoming request
   *
   * @example "America/Chicago"
   */
  timezone?: string;
  /**
   * If known, the ISO 3166-2 name for the first level region associated with
   * the IP address of the incoming request
   *
   * @example "Texas"
   */
  region?: string;
  /**
   * If known, the ISO 3166-2 code for the first-level region associated with
   * the IP address of the incoming request
   *
   * @example "TX"
   */
  regionCode?: string;
  /**
   * Metro code (DMA) of the incoming request
   *
   * @example "635"
   */
  metroCode?: string;
};

Making all the properties optional handles the case where there is no data {} and making the country field a union of Iso3166Alpha2Code | 'T1' handles the TOR case.

Looking forward to seeing this patched. In the mean time I just have to modify my local node_modules/@cloudflare/workers-types on every install. Its pretty annoying. I can’t create my own fork since https://github.com/cloudflare/workers-types is no longer maintained. If you have a better suggestion for a stop gap that doesn’t involve // @ts-ignore I’m all ears.

Thanks!