Repoinit analyser

Lots of customer requests in regards to the transform job, to a degree of around half or so, are regarding failed repoinit statements failing in the transform job.

Usually these are regarding missing create path statements, leading to failing SetProperties or SetACL's.

We should fire up a in memory repository OakRepository and apply the customer repoinit statements to validate them, in the AEMAnalyser.

This will incur some delay in the build step, maybe a few minutes, but it could be a lot for some customers. Therefore, we should make it possible to:

-Toggle off the functionality using launch darkly

-Make it possible to skip the step in the maven plugin using a profile or a property

All in all it should be worth it in pretty much most cases, because the failure will appear locally or at least in the build step which is much faster, and clearer then the transform step.

It will save a lot of time in support and firefighting efforts.

Start by locating the AEMAnalyser and the Maven plugin entry points that process customer repoinit statements, then inspect how an in-memory OakRepository could be applied. Done means repoinit validation reports failures before the transform job, while LaunchDarkly and a Maven profile or property can skip the step.

Written by the indexing model from the issue text.