Add fluent logger to simplify logging

[oxsean]

What is the purpose of the change

The original ErrorTypeAwareLogger doesn't support string formatting, and cause, extendedInformation are absolutely mostly empty, so adding fluent wrappers to simplify the logging.
Meanwhile, we need modify the exception code inspect next step.

// Before:
    LOGGER.warn(
            PROTOCOL_FAILED_PARSE,
            "",
            "",
            String.format(
                    "Failed to parse request timeout set from:%s, service=%s " + "method=%s",
                    timeoutString, context.getServiceDescriptor().getInterfaceName(), context.getMethodName()));

// After
    LOGGER.warn(
            LoggerCodeConstants.PROTOCOL_FAILED_PARSE,
            "Failed to parse request timeout set from: {}, service={}, method={}",
            timeoutString,
            context.getServiceDescriptor().getInterfaceName(),
            context.getMethodName());

Brief changelog

Verifying this change

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.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud