fix: Allow defineConsts to take numbers as values with TypeScript

[dwei-figma]

What changed / motivation ?

There seems to be a divergence between the type of TTokens in Flow vs. in TypeScript. This causes defineConsts to reject number values in TypeScript, like so:

export const zIndex = stylex.defineConsts({
  // Type 'number' is not assignable to type 'string | CSSType<string | number | null> | { [key: string]: string; }'.ts(2322)
  connector: 1,
  bifurcatedPicker: 2,
})

Sync the type of TTokens in packages/@stylexjs/stylex/src/types/StyleXTypes.d.ts against that of packages/@stylexjs/stylex/src/types/StyleXTypes.js to fix this.

Additional Context

Test case added to packages/typescript-tests/src/typetests.ts.

Pre-flight checklist

• I have read the contributing guidelines
  Contribution Guidelines
• Performed a self-review of my code

[dwei-figma]

AtRuleStr is an alias for the template string type `@${string}` earlier in the file, so this should have no effect.

Was looking to understand why this restriction doesn't seem to currently apply to defineVars and defineConsts. Seems like it's because these two take a generic that extends TTokens instead of TTokens directly.

Not sure if our intention is to actually clamp down, but if we do, I can look into how to make this work.

[mellyeliu]

Changes look good - thanks for flagging this. We’ve historically optimized our types for flow, so ts has a few rough edges (see also: #1024) that we've been slowly working through fixing.