--bazel not using relative path in cache files for imports

Bug Report

if i create a python file file_a.py and a file file_b.py and i make file_b import file_a and i the run mypy --bazel file_b.py, then the paths in the meta.json and data.json files are relative in the cache files for file_b but absolute in cache files for file_a. I would expect mypy to use relative paths everywhere in bazel mode.

If I run directly on file_a (mypy --bazel file_a.py) i get relative paths in the cache files for file_a.

To Reproduce

Create file_a.py and file_b.py as described above, run mypy --bazel file_b.py.

Expected Behavior

Relative paths in all produced cache files. Also same hash and interface hash in the cache files for file_a produced by running on file_b that imports file_a, as if I had run directly on file_a.

Actual Behavior

Absolute path on cache files for imports. Also differing hash and interface hash of the cache files, if run on as an import vs. run on directly.

Your Environment

• Mypy version used: 1.8.0 (Same behavior with other versions)
• Mypy command-line flags: --bazel
• Mypy configuration options from mypy.ini (and other config files): N/A
• Python version used: 3.11 (Same behavior with other versions)

Reproduce the issue with file_a.py importing file_b.py and run mypy --bazel file_b.py, then compare the meta.json and data.json cache files with those produced by running directly on file_a.py. Done means imported-file caches use relative paths and have the same hash and interface hash as direct-run caches.