### Bug Description The new collision handling between overlay and stage is reporting issues on symlinks. In the included example, the path `usr/lib/ssl/cert.pem` is present in both the overlay and the part's install dir, and is a symlink in both cases. However, the overlay symlink points to an absolute path: ``` lrwxrwxrwx 1 root root 34 Feb 5 2025 cert.pem -> /etc/ssl/certs/ca-certificates.crt ``` ... while the file coming from the stage-package is a relative symlink: ``` lrwxrwxrwx 1 root root 42 Sep 10 14:11 cert.pem -> ../../../etc/ssl/certs/ca-certificates.crt ``` It's a relative symlink because of the way craft-parts handles stage-packages, which is correct. However, in this case maybe both files should be considered "the same" since they will ultimately resolve to the same path in the payload (for Rockcraft and Imagecraft at least). As an aside, these absolute symlinks from the overlay are dangerous when they staged, as they now point to the build system (which is wrong) and will give wrong results if a part uses them. That's unrelated to this specific issue, which is only about the bad collision itself. ### To Reproduce Use Rockcraft 1.14 to build the attached part. ### part yaml ```shell parts: my-part: plugin: nil overlay-packages: [openssl] stage-packages: [openssl] ``` ### Relevant log output ```shell Failed to stage: parts list the same file or directory with different contents or permissions. Detailed information: Part 'my-part' and the overlay of part 'my-part' list the following files, but with different contents or permissions: usr/lib/ssl/cert.pem usr/lib/ssl/certs usr/lib/ssl/openssl.cnf usr/lib/ssl/private ```