[FEATURE] (type-safe-api) Better code generation for "default" responses in OpenAPI

### Describe the feature

OpenAPI lets you define a [default response](https://swagger.io/docs/specification/v3_0/describing-responses/#default-response).

Currently code generation treats this as a `0` response code, however we should generate code which conforms better to the specification.

### Use Case

More intuitive behaviour for a given OpenAPI spec.

### Proposed Solution

* Handler wrappers should allow returning any response code (ideally other than other defined responses) with alongside the modelled response.
* Clients/hooks should deserialise responses to the appropriate modelled response for any default responses with 2XX codes. Possibly combine with #821 to deserialise error responses too.

### Other Information

_No response_

### Acknowledgements

- [X] I may be able to implement this feature request
- [X] This feature might incur a breaking change

### PDK version used

0.23.60

### What languages will this feature affect?

Typescript, Java, Python

### Environment details (OS name and version, etc.)

OSX

The issue names no files or tests, so start by locating the type-safe-api generator's handling of OpenAPI default responses across the TypeScript, Java, and Python outputs. Review the current `0` response-code behavior and related issue #821 before defining compatible handler and client/hook behavior. Done means default responses follow the OpenAPI specification without incorrectly treating them as status code 0.

Written by the indexing model from the issue text.