feat: optimize MethodConfigTest

[Linchen-Xu]

What is the purpose of the change

Optimize code in MethodConfigTest, and add a new test.

Brief changelog

• Remove unnecessary exception throw code
• Add the convertMethodConfig2AsyncInfo test in the MethodConfigTest class in dubbo-config-api module, which was added in dubbo-compatible module.
• The MethodConfigTest class in the dubbo-compatible module should test MethodConfig class in com.alibaba.dubbo.config package instead of the class with the same name in org.apache.dubbo.config package, which is tested in another test class.
• Remove the unnecessary manual cast from String type to Object type when calling assertEquals and assertThat, the type erasure mechanism will do it (the matcher will eventually be treated as Matcher<Map> instead of Matcher<Map<Object, Object>>).

Verifying this change

run both MethodConfigTest.

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

No Coverage information
0.0% Duplication