[8.1.0] Rollforward of https://github.com/bazelbuild/bazel/commit/7f6e6496726aad4038368979c772e944bc323b7f: Add support for path mapping to CppArchive

[bazel-io]

This mostly requires wiring up the existing machinery for structured variables and (most) link build variables.

Utility methods on PathMappers are moved to PathMapper so that they can be dependend on by AbstractCommandLine without creating a cycle.

NEW:

• Allow toolchain variables to be None and skip them in that case, matching the previous behavior.
• Use the effective output paths mode for fingerprinting to preserve action cache entries for non-path mapped actions even when path mapping is generally enabled.

Closes #25154.

PiperOrigin-RevId: 721850758
Change-Id: I34a66006ba4c8fd73d62ce8cea249577f62a1b02

Commit 08f0709

[fmeum]

You can merge this PR to fix the build: bazel-io#3

The diff:

--- a/src/test/java/com/google/devtools/build/lib/rules/cpp/LinkBuildVariablesTest.java
+++ b/src/test/java/com/google/devtools/build/lib/rules/cpp/LinkBuildVariablesTest.java
@@ -513,7 +513,9 @@ public class LinkBuildVariablesTest extends LinkBuildVariablesTestCase {
 
     assertThrows(
         ExpansionException.class,
-        () -> testVariables.getVariable(LinkBuildVariables.IS_CC_TEST.getVariableName()));
+        () ->
+            testVariables.getVariable(
+                LinkBuildVariables.IS_CC_TEST.getVariableName(), PathMapper.NOOP));
 
     ConfiguredTarget binaryTarget = getConfiguredTarget("//x:foo");
     CcToolchainVariables binaryVariables =
@@ -521,7 +523,9 @@ public class LinkBuildVariablesTest extends LinkBuildVariablesTestCase {
 
     assertThrows(
         ExpansionException.class,
-        () -> binaryVariables.getVariable(LinkBuildVariables.IS_CC_TEST.getVariableName()));
+        () ->
+            binaryVariables.getVariable(
+                LinkBuildVariables.IS_CC_TEST.getVariableName(), PathMapper.NOOP));
   }
 
   @Test

[iancha1992]

@fmeum fixed! Thank you