Add supports-path-mapping execution info by default for actions that support it

### Description of the feature request:

Currently if you want to use path stripping with C++ you need something like this in your bazelrc:

```
common --incompatible_modify_execution_info_additive
build --modify_execution_info=CppArchive=+supports-path-mapping
build --modify_execution_info=CppCompile=+supports-path-mapping
build --modify_execution_info=CppModuleMap=+supports-path-mapping
build --modify_execution_info=Objc.*=+supports-path-mapping
build --experimental_output_paths=strip
```

I think since this feature is gated behind `--experimental_output_paths=strip` it would be safe to add `execution_requirements = {"supports-path-mapping": "1"}` to these actions automatically (maybe excluding `CppArchive`), so that only the 1 flag has to be passed to enable this. If for some reason a user wanted to use path mapping but disable C++ support, presumably they could pass something like `--modify_execution_info=CppCompile=-supports-path-mapping`. This would make it less error prone to use this feature where you can accidentally omit a mnemonic, or not get new ones enabled as they are supported

### Which category does this issue belong to?

_No response_

### What underlying problem are you trying to solve with this feature?

_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

```

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

_No response_

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

_No response_