jsc.paths following symlinks under bazel when it should not

[Aghassi]

Describe the bug

This has been filed before via #8757 and tracked here aspect-build/rules_swc#216 (comment). Namely, when using jsc.paths with baseURL equal to . the swc transform follows the symlink too far and creates a very deeply traversed path. I don't have much useful information beyond that, just that I would expect a string replace and not a full path resolution which includes a symlink.

Input code

No response

Config

{
  "$schema": "https://json.schemastore.org/swcrc",
  "sourceMaps": "inline",
  "jsc": {
    "parser": {
      "syntax": "typescript",
      "tsx": true
    },
    "target": "es2022",
    "transform": {
      "react": {
        "runtime": "automatic"
      },
      "hidden": {
        "jest": true
      }
    },
    "baseUrl": ".",
    "paths": {
      "@webpack-aliases/css": ["src/client/css/index.js"]
    }
  },
  "module": {
    "type": "es6"
  },
  "isModule": true,
  "minify": false
}

### Playground link (or link to the minimal reproduction)

None from the playground because I can't repro it in the playwground

### SWC Info output

_No response_

### Expected behavior

I'd expect under bazel and rules_swc that this symlink resolve correctly as it would outside. But right now it seems not to be. 

### Actual behavior

The path injected into the transformed code has `../../../private/var` in it when it should just start with `./`

### Version

1.6.6

### Additional context

_No response_

[kdy1]

Please provide a minimal reproduction