Add normalizedArguments as japiCmp task input instead of rule arguments

[jprinet]

Issue

the japiCmpTask is not relocatable when using rule arguments with absolute paths. Here is an example in the micronaut-build project.

The cost of this with a relocated build is 1mn23s on the micronaut-core build

Here is the build scan comparison illustrating the volatile inputs

Fix

This PR adds a rule constructor which allow to add a normalized version of the arguments which will be used as rule inputs. The consumer would then call this constructor with normalized are arguments, here is how in the micronaut-build:

report.addViolationTransformerWithNormalization(AcceptedApiChangesRule.class,
                                    Collections.singletonMap(AcceptedApiChangesRule.CHANGES_FILE, changesFile.getAbsolutePath()),
                                    Collections.singletonMap(AcceptedApiChangesRule.CHANGES_FILE, project.relativePath(changesFile.getAbsolutePath()))
)

Question

This PR only addresses the ViolationTransformer rule type, do all subtypes of RuleConfiguration have to be addressed the same way?

[jprinet]

Closing this after discussion with @melix.

• Duplicating the rule arguments is not a good approach
• Blindly trying to apply a relative path normalization to any rule argument does not sound quite right

The ideal solution would be to have a type to support those (StringWithPath?)