Uniform behaviour for the methodInvocations that are needed for template unsubstitution

[Jenson3210]

What's changed?

Added an overload to Substitutions maybeParameter that accepts the prefixed element.
When using a template that passes in a placeholder that must be replaced by an Object / parameter, the resulting template is shows as __P__.<java.lang.Object>/*__p0__*/p()

The existing code will pass methodName's Identifier (/*__p0__*/p()) to the maybeParameter call which will cause it to use the prefix of this Identifier to parse the template resulting in trimmed template prefix.

By overloading and passing the entire methodInvocation for prefix calculations we no longer need to overcome this in every recipe that is using templates but we can just rest assured that the prefix of the template will be also present in the result lst objects.

What's your motivation?

Stumbled into this investigation with @Laurens-W after having some other template issues.

Checklist

• I've added unit tests to cover both positive and negative cases
• I've read and applied the recipe conventions and best practices
• I've used the IntelliJ IDEA auto-formatter on affected files

[Jenson3210]

Do not merge this one without approval from @jkschneider