CppArchive path-mapping generated files issue

### Description of the bug:

Currently if you enable path-mapping for CppArchive, the archive points to generated files at a path that isn't valid outside of the path mapped action. Ideally there would be a way to make this work for common C++ debugging workflows

### Which category does this issue belong to?

_No response_

### What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

_No response_

### Which operating system are you running Bazel on?

_No response_

### What is the output of `bazel info release`?

_No response_

### If `bazel info release` returns `development version` or `(@non-git)`, tell us how you built Bazel.

_No response_

### What's the output of `git remote get-url origin; git rev-parse HEAD` ?

```text

```

### If this is a regression, please try to identify the Bazel commit where the bug was introduced with bazelisk --bisect.

_No response_

### Have you found anything relevant by searching the web?

_No response_

### Any other information, logs, or outputs that you want to share?

_No response_

Start by reproducing the issue with CppArchive and path-mapping enabled, then inspect how generated-file paths are recorded in the archive. The work is done when archived paths remain valid outside the path-mapped action and support the stated common C++ debugging workflows.

Written by the indexing model from the issue text.