feat(logging): #13378 Uniformly uses log4j2 as the logging component

[oxsean]

What is the purpose of the change

Currently in Dubbo, there is a mixed use of log components, and some modules lack log configuration, due to no log output. Therefore, uniformly use log4j2 can reduce the learning and cost, reduce logging component conflicts

Brief changelog

1. Replace log4j and logback with log4j2, providing a simple Log4j2 configuration. Unfortunately log4j2 does not support native, so have to use logback, update future while log4j2 support native.

2. Adjusted versions of some artifacts in pom.xml to unify them as much as possible to the BOM.

Verifying this change

ci passed

Checklist

• Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
• Each commit in the pull request should have a meaningful subject line and body.
• Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
• Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
• Add some description to dubbo-website project if you are requesting to add a feature.
• GitHub Actions works fine on your own branch.
• If this contribution is large, please follow the Software Donation Guide.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

0.0% Coverage
0.0% Duplication