Added Profile dependency migration

[marcel-gepardec]

Profile dependency migration

What's changed?

Dependencies can now be migrated within the profile section whether there are inside of a dependencyManagement section or declared as normal dependencies. That's why profile dependency validations are now added to the MavenVisitor class.

Example:

Before:

...
<profiles>
        <profile>
            <id>test</id>
            <dependencies>
                <dependency>
                    <groupId>javax.persistence</groupId>
                    <artifactId>javax.persistence-api</artifactId>
                    <version>2.2</version>
                </dependency>
            </dependencies>
        </profile>
</profiles>
...

After:

...
<profiles>
        <profile>
            <id>test</id>
            <dependencies>
                <dependency>
                    <groupId>jakarta.persistence</groupId>
                    <artifactId>jakarta.persistence-api</artifactId>
                    <version>3.2.0</version>
                </dependency>
            </dependencies>
        </profile>
</profiles>
...

What's your motivation?

A question was posted on slack by @ErhardSiegl referring the not migrating dependencies inside profiles.
Regarding this problem I took the initiative and implemented it.

Have you considered any alternatives or workarounds?

While working on this topic, I noticed a missing recipe for plugins and profiles. While it is possible to add profiles or change plugin dependencies, there are no options to change a dependency groupId, artifactId, or version within plugins or profiles separately. Just a heads up, maybe consider implementing a recipe to be able to change this in the future.

[timtebeek]

Thanks a lot! I've pushed some minor changes up to #4311 as I can't push to this pull request. Should be good to merge soon.