Replace TransitionApplier interface with a dedicated class.

This accomplishes a few goals:

 1. Removes the outdated BuildConfiguration.StaticConfigurationApplier code.
 2. Removes the TransitionApplier abstraction completely. This was an awkward
    bridge meant to support both static and dynamic implementations.
 3. Moves transition logic to its own dedicated class: ConfigurationResolver.
    This no longer belongs in BuildConfiguration, which we ultimately want to
    become a simple <key, value> map.

Part of the static config cleanup effort.

PiperOrigin-RevId: 165736955

1 files changed, 1 insertions, 2 deletions

diff --git a/src/main/java/com/google/devtools/build/lib/skyframe/BuildConfigurationFunction.java b/src/main/java/com/google/devtools/build/lib/skyframe/BuildConfigurationFunction.java
index 266b320fe7..e335ceaa71 100644
--- a/src/main/java/com/google/devtools/build/lib/skyframe/BuildConfigurationFunction.java
+++ b/src/main/java/com/google/devtools/build/lib/skyframe/BuildConfigurationFunction.java
@@ -76,8 +76,7 @@ public class BuildConfigurationFunction implements SkyFunction {
             directories,
             fragmentsMap,
             key.getBuildOptions(),
-            workspaceNameValue.getName(),
-            ruleClassProvider.getDynamicTransitionMapper());
+            workspaceNameValue.getName());
     return new BuildConfigurationValue(config);
   }