[Feature] Migration skywalking from Junit4 to Junit5

[GOODBOY008]

Search before asking

• I had searched in the issues and found no similar feature requirement.

Description

The main motivations are:

• Making full use of Java 8 Lambdas for writing easier to read tests and a
  better performing way of composing failure messages.
• Improved test structures with nested and dynamic tests.
• Much better support for parameterized tests to avoid separating
  parameterized and non-parameterized parts into different test classes.
• Composable dependencies and better hooks for advanced use cases.
• Better exception verification
• More current infrastructure
• Better parallelizable

Use case

No response

Related issues

No response

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[wu-sheng]

If you want to do this, I am fine. But notice, there are several Java repositories, backend and agent are major.

[wu-sheng]

But the work will be huge, and this wouldn't be easy to review.

[lujiajing1126]

As I understand, if we are using powermock, migrating to Junit5 may not be possible due to the upstream issue powermock/powermock#929.

[wu-sheng]

@lujiajing1126 Thank you for updating. And yes, powermock is common in our UTs. I am moving this to discussion for now.

[GOODBOY008]

We can migrate step by step to complete this work,when powermock support Junit5.This also will confuse developer when Junit4 mixed with Junit5.