generating invalid TypeScript import path with using Cargo workspace

[h-michael]

Hi, thanks for your excellent work. I love ts-rs.

I use ts-rs with the project which uses Carog workspace. I found the following issue.
If that project has crates on both the grandchildren directory and child directory, it may generate an invalid TypeScript import path.
I created example project.
This struct uses another crate's struct that crates on the grandchildren directory.
In this case, invalid import paths are generated.
That should be as follows.

import type { A } from "./A";
import type { B } from "./B";

I know this is a corner case. I can avoid this by using a flattened directory architecture. But actually, I use ts-rs with a bigger mono repository than the above example. So I want to use nested directories to categorize crates.

If you can give me some guidelines to fix this problem, I can create PR to fix it. Thanks.

[escritorio-gustavo]

Fixed by #221 and #218