fix: Use "any" for types without a primitive mapping
This should result in TypeScript models being generated even when the exact type can't be translated into TypeScript by using the "any" type. It may be more appropriate to use the "unknown" type in the future.
This should make the models more usable and less error prone until we get stricter typing in place.
Signed-off-by: Daniel Bluhm firstname.lastname@example.org