Runfiles::Create does not work with `.stripped` binary

### Description of the bug:

Creating a [`Runfiles`](https://github.com/bazelbuild/bazel/blob/master/tools/cpp/runfiles/runfiles_src.h) instance with `Runfiles::Create(argv[0], nullptr)` works within a `cc_binary(name = "foo", ...` if run as `bazel run :foo`, but if the `.stripped` target is used instead, the creation fails (and thows an exception): `bazel run :foo.stripped`.

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

Make a `cc_binary` with content like https://github.com/bazelbuild/bazel/blob/881fc800fdd76773a4b229a64673bc3b8feb9745/tools/cpp/runfiles/runfiles_src.h#L34-L37, then run the stripped binary, either via `bazel run`, or via `bazel build` and then call the binary directly.

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

Linux

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

release 5.1.1

### 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 master; git rev-parse HEAD` ?

_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 with tools/cpp/runfiles/runfiles_src.h and reproduce the issue using a minimal cc_binary, comparing bazel run :foo with bazel run :foo.stripped or a directly built stripped binary. Trace why Runfiles::Create(argv[0], nullptr) throws for the stripped target; done means the same creation succeeds without an exception for both targets.

Written by the indexing model from the issue text.