feat: Improve Object Type Handling in Zod Conversion

[Yoon-Hae-Min]

Why

• When defining an object type within an object, it is inferred as any when converted to Zod.
  

• any is a supertype of object, necessitating a stronger assertion of the type.

• After generating the type, during validation, any includes optional, which leads to a mismatch with the original type.
  

• This issue is resolved by treating the object as record any. => z.record(z.any())

Result

case 1: primitive object

export type Obj = object;

// Generated by ts-to-zod
import { z } from "zod";

export const objSchema = z.record(z.any());

case 2: object in object

export interface ExampleObject {
  result: object;
}

// Generated by ts-to-zod
import { z } from "zod";

export const exampleObjectSchema = z.object({
  result: z.record(z.any()),
});

Test

I added a test case related to this PR.

[tvillaren]

Thanks for your addition!