Unintuitive semantics for imported project from a different folder

To illustrate what the title means, here is an example: when `A/cabal.project` imports `A/B/cabal.project`, I observe that inside the `A/B/cabal.project` packages, the package path is based on A, instead of more intuitively `A/B`.

An live example is [here](https://github.com/yolc-dev/yul-dsl-monorepo/blob/master/cabal.project) which has an import: `import: 3rd-parties/cabal.project`.

Cabal version 3.14