fix(java): correctly inherit version and scope from upper/root depManagement and dependencies into parents

[DmitriyLewen]

Description

Forward dependencyManagement and Properties field from root/upper POM into parents.
dependencyManagement should be used as non-root dependencyManagement

See new test for more details.

Related issues

• Close bug(pom): wrong inheritance of version and scope from root DepManagement in parent dependencies #7539

Related PRs

• fix(java): use dependencyManagement from root/child pom's for dependencies from parents [backport: release/v0.55] #7521

Checklist

• I've read the guidelines for contributing to this repository.
• I've followed the conventions in the PR title.
• I've added tests that prove my fix is effective or that my feature works.
• I've updated the documentation with the relevant information (if needed).
• I've added usage information (if the PR introduces new options)
• I've included a "before" and "after" example to the description (if the PR is a user interface change).

[knqyf263]

I have found out that we have probably been making a mistake for a while. We're currently evaluating the parent POM first and then merge it into the child POM, but it seems correct to merge the dependencies, dependencyManagement and properties of the parent POM into the child POM before evaluating it. In fact, I implemented it that way and it simplified things considerably.
However, I'm likely missing something. You will point out something as usual 😄

[DmitriyLewen]

I tested your changes with user issue (#7537).
I also tested the cases I could think of.
I also updated one test case (added nested parents).

And looks like your changes work correctly 👍

[knqyf263]

Thanks for testing. It is rare that I correctly implement it once 🤣
It was good to realize the mistakes in the parent POM implementation and to be able to simplify it.