fix: ts support for all optional keys in data model

[jrozbicki]

Closes #5272

Is object extends T different than T extends object?

Before: Following basic example, if Person had only optional fields DeepKeys would use object extends T and infer string

type Person = {
  firstName?: string
  lastName?: string
  age?: number
  visits?: number
  status?: string
  progress?: number
  address?: {
    city?: string
  }
}

type Test = DeepKeys<Person>
   // ^? type Test = string

After: When that got removed, the same case will fall under T extends object and will nicely infer key names.

type Person = {
  firstName?: string
  lastName?: string
  age?: number
  visits?: number
  status?: string
  progress?: number
  address?: {
    city?: string
  }
}

type Test = DeepKeys<Person>
   // ^? type Test = "firstName" | "lastName" | "age" | "visits" | "status" | "progress" | "address" | "address.city"

Did I missed something obvious? It was probably there for a reason

[KevinVandy]

I tested this for a while, and it looks good. We can revert if something pops up

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit b4ea6f3. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 1 target

• nx affected --targets=test:format,test:sherif,test:knip,test:lib,test:types,build --parallel=3

---

Sent with 💌 from NxCloud.