[Dubbo-267] Fix protobuf type lose field when deepCopy inJvmInvoker …

[vio-lin]

What is the purpose of the change

修复INJVM模式下 Protobuf对象，不能被正常深度拷贝
问题复现

@Test
    public void testProtobufDeepCopy1() throws InvalidProtocolBufferException {
        SerializeSecurityManager serializeSecurityManager = FrameworkModel.defaultModel().getBeanFactory().getOrRegisterBean(SerializeSecurityManager.class);
        serializeSecurityManager.setCheckStatus(SerializeCheckStatus.WARN);
        ProtobufUtils.marshaller(GooglePB.PBRequestType.getDefaultInstance());
        ParamDeepCopyUtil paramDeepCopyUtil = new DefaultParamDeepCopyUtil();
        GooglePB.PhoneNumber phoneNumber = GooglePB.PhoneNumber.newBuilder()
            .setNumber("134123781291").build();
        List<GooglePB.PhoneNumber> phoneNumberList = new ArrayList<>();
        phoneNumberList.add(phoneNumber);
        Map<String, GooglePB.PhoneNumber> phoneNumberMap = new HashMap<>();
        phoneNumberMap.put("someUser", phoneNumber);
        GooglePB.PBRequestType request = GooglePB.PBRequestType.newBuilder()
            .setAge(15).setCash(10).setMoney(16.0).setNum(100L)
            .addAllPhone(phoneNumberList).putAllDoubleMap(phoneNumberMap).build();
        GooglePB.PBRequestType copyResult = paramDeepCopyUtil.copy(mockURL(), request, GooglePB.PBRequestType.class);
        String jsonString = ProtobufUtils.serializeJson(request);
        String jsonString2 = ProtobufUtils.serializeJson(copyResult);
        // hession 的深度拷贝会导致  jsonString2 = {}
        assertEquals(jsonString, jsonString2);
    }

Brief changelog

dubbo-spi-extensions\dubbo-serialization-extensions\dubbo-serialization-protobuf\src\test\java\org\apache\dubbo\common\serialize\protobuf\support\ProtobufParamDeepCopyUtilTest.java

dubbo-spi-extensions\dubbo-serialization-extensions\dubbo-serialization-protobuf\src\main\resources\META-INF\dubbo\internal\org.apache.dubbo.rpc.protocol.injvm.ParamDeepCopyUtil

Verifying this change

增加一个wraper 扩展，假如继承protobuf的接口，则使用另外的序列化器。

Follow this checklist to help us incorporate your contribution quickly and easily:

• 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.
• Format the pull request title like [Dubbo-XXX] Fix UnknownException when host config not exist #XXX. 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.
• 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.
• Run mvn clean install -DskipTests=false & mvn clean test-compile failsafe:integration-test to make sure
  unit-test and integration-test pass.
• If this contribution is large, please follow
  the Software Donation Guide.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (07416c0) 25.07% compared to head (95f5590) 25.13%.

Additional details and impacted files

@@             Coverage Diff              @@
##              3.2.0     #268      +/-   ##
============================================
+ Coverage     25.07%   25.13%   +0.06%     
- Complexity     1002     1007       +5     
============================================
  Files           284      285       +1     
  Lines         13134    13154      +20     
  Branches       1700     1703       +3     
============================================
+ Hits           3293     3306      +13     
- Misses         9503     9511       +8     
+ Partials        338      337       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[vio-lin]

这个工程的branch都是怎么管理的呢。
提交都在master 然后picup到 3.2等分支？

[songxiaosheng]

这个工程的branch都是怎么管理的呢。 提交都在master 然后picup到 3.2等分支？

修复bug可以在master 3.2.0是兼容3.2的功能分支（也会同步master分支代码），后续3.2分支兼容完成之后会合并到master

[songxiaosheng]

LGTM