Inconsistent behavior for optional properties with defaults

Description

I've discovered inconsistent behavior when generating types for optional fields which also provide a default value. See sandbox for more info

Given a simple Item schema:

"Item": {
    "type": "object",
    "properties": {
        "status": { "type": "string", "nullable": true, "default": "complete" },
    }
}

Depending on where it is defined in the openapi spec file we get different results:

If we define Item in the endpoint directly without using a ref we get:

"application/json": {
    /** @default complete */
    status?: string; // correct behavior
};

If we define Item in components and use a ref in the endpoint spec the result becomes:

Item: {
    /** @default complete */
    status: string; // this is now no longer optional
};

The latter behavior is unexpected and incorrect as the field should not be required

Name	Version
`openapi-typescript`	`7.4.1`
Node.js	`20.12.1`

Reproduction

see spec.json input file and output.d.ts result

Checklist

[x] My OpenAPI schema passes the Redocly validator (npx @redocly/cli@latest lint)
[ ] I’m willing to open a PR (see CONTRIBUTING.md)

openapi-ts / openapi-typescript