Use execution info instead of hard-coded mnemonics for Java path mapping

[fmeum]

By removing Java rules from the hard-coded mnemonics allowlist for path mapping, users can rely on --modify_execution_info to selectively disable path mapping for them just like for Starlark actions.

This requires fixing two minor inconsistencies in how execution info is populated for Java actions:

• In JavaCompilationHelper, buildKeepingLast is used instead of buildOrThrow to prevent a crash when a target sets supports-path-mapping via tags.
• In JavaHeaderCompileAction, --experimental_inmemory_jdeps_files no longer causes all other execution info to be lost.

Fixes #21092

[fmeum]

@hvadehra Could you review this? While the aim is to remove tech debt related to the path mapping feature, the PR almost exclusively touches execution info logic for Java actions.

CC @aranguyen

[fmeum]

@bazel-io fork 7.1.0

[iancha1992]

Just FYI, this is being imported in cl/606319644

cc: @bazelbuild/triage @Wyverald @meteorcloudy

[justinhorvitz]

I just traced a memory regression to this change. It only shows up in builds that use --experimental_inmemory_jdeps_files so I think it's actually due to the fix mentioned in the description:

In JavaHeaderCompileAction, --experimental_inmemory_jdeps_files no longer causes all other execution info to be lost.

The magnitude of the regression is about 0.2% on our benchmark java-heavy build. Given that it's actually a fix, we won't roll this back. Instead, I'll keep in mind a couple idea:

1. Is there a more efficient representation for execution info than ImmutableSortedMap?
2. For in-memory jdeps, we miss out on the benefit interning the execution info (see SpawnAction constructor) because we put a unique value in the map ( outputDepsProto.getExecPathString()). We can either find a way to avoid the unique entry, or just skip interning, since it has memory overhead without the benefit.

[fmeum]

Good find, I didn't think of that.

I'm not aware of any other execution info entry with a unique value. As a quick win, we could just not inline infos containing this particular key in the SpawnAction constructor.

Maybe a custom SortedMap implementation that stores the unique part separately from the interned constant part could improve the savings further?

[justinhorvitz]

I have https://bazel-review.googlesource.com/c/bazel/+/242796 out for review, which reduces memory on the internal benchmark target by 1.0%. So it ends up even better than before your PR.

There might be more savings to be had by using something other than a map, but it also might be negligible so long as interning is effective.

[fmeum]

@bazel-io fork 7.1.1

[fmeum]

@iancha1992 Forking again for the fix in #21093 (comment).

[justinhorvitz]

Memory improvement submitted as e8d844e.