Make ExtractExplicitConstructorInvocationArguments templates context-free

[knutwannheden]

Motivation

ExtractExplicitConstructorInvocationArguments (JEP 513) applied both of its JavaTemplates with contextSensitive(). Context-sensitive templating reconstructs and reparses the enclosing class and method on every application, which is the dominant cost when the recipe actually fires. Neither template needs it: contextSensitive() only reconstructs the surrounding local scope (leading variable declarations, method parameters) into the parse stub — it does not govern type resolution. Every type these templates declare is the type of an existing super(..)/this(..) argument, so it is already present in the unit, resolves via the shared JavaTypeCache, and the spliced result is re-attributed against the real cursor afterward. Dropping contextSensitive() therefore produces byte-identical, fully type-attributed output while skipping the enclosing-context reparse.

Summary

• Drop contextSensitive() from both templates (the local-variable declarations and the argument-list rewrite).
• Bail on the cheapest decisive check — no method-invocation/object-creation argument — before any variable-name generation, cursor-scope scanning, or templating, so a constructor the recipe will not touch pays nothing.
• Add two regression tests that lock in the type-attribution behavior the context-free path must preserve: one where the extracted variable's type is a source-path-only type defined in a sibling source, and one where the extracted variable is declared with a widening source-path supertype that is referenced nowhere else in the unit. They assert the rewritten reference keeps its variable binding (fieldType) and the extracted declaration keeps a resolved fully-qualified type (not Unknown).

Test plan

• ExtractExplicitConstructorInvocationArgumentsTest passes (all existing cases plus the two new source-path regression tests).
• New tests assert post-recipe type attribution via afterRecipe: the super(..) reference has a non-null type and fieldType, and the extracted declaration's type resolves to a real FQ type.