tree fef12d823aac238fe593e556b55be0b9edbd53d4
parent 10fd043243e9df7be026783758cfdb4c67c1ccd9
author Googler <shahan@google.com> 1685191045 -0700
committer Copybara-Service <copybara-worker@google.com> 1685191165 -0700

Add rule-transition to front of ConfiguredTargetFunction

Also memoizes computation of TargetAndConfiguration.

RELNOTES:
As a transitional step in a larger refactoring, rule transitions
are applied twice. Once during dependency resolution and once right before
analysis of those rules. After the refactoring is complete, rule transitions
will be applied only once.

Rule transitions are mostly expected to be idempotent, in which case this is
a no-op. For transitions where that is not the case, this could be a breaking
change or a cause a build performance regression.

PiperOrigin-RevId: 535843026
Change-Id: Icfad5a4a84081b7b63ca560ebed97c478cd6e2d4