Add common lombok config

[Tristan-WorkGH]

Please check if the PR fulfills these requirements

• The commit message follows our guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

Does this PR already have an issue describing the problem?
No.

What kind of change does this PR introduce?
Add a profile (inactive by default) to be use by children projects by activating the correct profile.
It consist of:

• the common base of lombok configuration in the /lombok.config to be reuse by children
• a check that the configuration is correctly referenced in the project using it

What is the current behavior?
Each projects have their own lombok.config with duplication and often incomplete.

What is the new behavior (if this is a feature change)?
Each children project can have a common base and update can be centralized.

Does this PR introduce a breaking change or deprecate an API?
No.

Other information:
The idea is to use lombok's import feature to have a common base for GridSuite projects.

Projects that want to use this project will need to:

• have this module as parent
• activate this profile: (one of the following)
  • using command line with -Plombok-config-copy and -Plombok-config-check
  • create the file .mvn/lombok-config-copy in the project to activate the copy of the file to be used
  • optionally create the file .mvn/lombok-config-check in the project to activate the check that lombok.config contains the import
• add this line at the start of /lombok.config

  import target/configs/powsybl-build-tools.jar!powsybl-build-tools/lombok.config

This profiles will, when activate:

1. during initialize phase: copy the powsybl-build-tools jar in target/configs/ (to be found and use by lombok)
2. during validate phase: check that the lombok.config file have the correct import at the start of the file

This has been tested with Maven, JetBrains IDEA IntelliJ and Eclipse (with m2e + lombok plugin).

The initialize has been use because of its early position in (Maven lifecycle)[https://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html], as IDEs seems to run this phase when reloading/refreshing the project and we need the jar to be present for IDE to parse the configuration (when editing files).

Side note:
No better way found, mainly because of limitation in the way lombok manage internally the import path (ConfigurationFile and FileSystemSourceCache).
And that will not change in near future.

[Tristan-WorkGH]

Due to limitation in Maven profiles activation system, like in #2, we use a system of file markers to activate a profile from child projects.

Another note is during my tests, it seems we can't have multiple conditions like <file/> + <property/> or <file><exists/><exist/></file>, as maven only check the first condition...
So the following don't work for activate if a file exist and another not exist at same time: <file><exists>file1</exists><missing>file2</missing></file>

PR description updated

[Tristan-WorkGH]

@jonenst I found this other method to copy/extract only the lombok.config from the jar instead of copying the jar lib. A preference?

<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-dependency-plugin</artifactId>
    <executions>
        <execution>
            <id>lombok-unpack-config</id>
            <phase>initialize</phase>
            <goals>
                <goal>unpack</goal>
            </goals>
            <configuration>
                <artifactItems>
                    <artifactItem>
                        <groupId>com.powsybl</groupId>
                        <artifactId>powsybl-build-tools</artifactId>
                        <version>${powsybl-build-tools.version}</version>
                        <type>jar</type>
                        <outputDirectory>${project.build.directory}/configs</outputDirectory>
                        <includes>powsybl-build-tools/lombok.config</includes>
                        <overWrite>true</overWrite>
                    </artifactItem>
                </artifactItems>
            </configuration>
        </execution>
    </executions>
</plugin>

[jonenst]

separate PR